Skip to content
Claim this template

Free course template · Global

Secure AI-assisted software development: Coding assistants and agents without the risk

A ready-made course, live deck and two surveys for software developers. AhaSlides tracks progress, completion and scores for you. 45 minutes, 6 lessons, 12-question final check. Last reviewed 21 October 2026; not legal advice.

Claim the templatePreview the courseDownload SCORM for your LMS

Free. No credit card. Edit everything.

Course outline at a glance

  • The package that did not exist
  • The chain
  • Timeline
  • Quiz

  • Six failure modes
  • Spot the flaw
  • Flashcards
  • Sorting activity
  • Multi-select quiz

  • Prompt, inspect, test, disclose
  • Share or never share
  • Process
  • Sorting activity
  • Quiz

  • The stack trace
  • The agent and the issue
  • The untested pull request
  • Scenario
  • Multi-select quiz

  • Approved set-up
  • Labelling and review
  • Accordion
  • Process
  • Quiz

Final check: 12 questions, 80% to pass

Try some questions from the course

Question 1 of 3

What should Priya have done before installing the suggested library?

 

She should have checked that the package exists, that her team approves it and that it is the library she expected, before installing anything. Asking the assistant to vouch for its own suggestion is not a check, and installing in a throwaway folder still runs the code on her machine.

Lesson 1, How a hallucinated package becomes an attack, teaches this. See the outline

Question 2 of 3

You paste a failing test's output into an approved assistant and notice it contains a customer's name and order number. What is the right habit?

 

Remove or replace the customer details before you share, and give only what the assistant needs, such as the error type and the relevant lines. Adding a request not to store the data does not stop it being stored, and pasting everything because the tool is approved ignores your data rules.

Lesson 3, The secure AI coding loop, teaches this. See the outline

Question 3 of 3

Why does your team ask you to label an AI-assisted pull request?

 

The label tells the reviewer to read closely, because assistant-written code can look finished and still hide flaws. It is not a mark of blame, and it does not replace review or testing.

Lesson 5, Approved tools, settings and AI-use pull request labelling, teaches this. See the outline

Try next questionClaim the template

Learners earn a certificate

Your organisation

Certificate of completion

This certifies that

Alex Morgan

has completed

Secure AI-assisted software development: Coding assistants and agents without the risk

Completed on12 October 2026
Sample certificate with a placeholder learner name.

Style 1 of 6: Teal humanist

Everyone who finishes gets a certificate with their name, the course title and the completion date. Add your own logo, colours and signer.

Three pieces that work together

Learners prepare on their own, you answer questions live, and the surveys tell you what stuck. 8 fields to fill in with your own policy, contacts and locations; each one is highlighted inside the course.

Claim the template
The Secure AI-assisted software development: Coding assistants and agents without the risk course as a learner first sees it

Completion is tracked for you

Learners sign in to take the course, so every start, finish and score is recorded in AhaSlides. No spreadsheet to keep.

  • Who has finished

    See who has not started, who is in progress and who has completed the course.

  • Every score

    Each learner's result on the 12-question final check, against the 80% pass mark.

  • What landed

    Survey results show what people took away, and the 30-day check-in shows whether they use it.

Claim the template

6 lessons, about 45 minutes

What learners can do at the end of each lesson. Minutes are an estimate.

  • Lesson 1: How a hallucinated package becomes an attack · 9 min

    Before you begin · The package that did not exist · The chain

  • Lesson 2: How coding assistants and agents fail · 8 min

    Six failure modes · Spot the flaw · Check

  • Lesson 3: The secure AI coding loop · 8 min

    Prompt, inspect, test, disclose · Share or never share · Check

  • Lesson 4: Grey areas: customer data, shell commands, untested pull requests · 8 min

    The stack trace · The agent and the issue · The untested pull request

  • Lesson 5: Approved tools, settings and AI-use pull request labelling · 6 min

    Approved set-up · Labelling and review

  • Lesson 6: Final assessment and secure coding acknowledgement · 6 min

    12 questions, 80% to pass. The result is saved to the learner's record.

Claim the template

Often taught together

Courses teams often run alongside this one.

Browse all templates (opens in a new tab)

Common questions

Yes. The course, the live deck and both surveys are free. Claiming the template into your AhaSlides account is free too.

Yes. The course is self-paced and online, and the live deck lets you add a live session in the room or online.

When a team adopts an assistant or agent; annually with the secure coding refresher.

Software developers, tech leads and DevOps engineers using AI coding assistants or agents; run by engineering leadership or application security.

Record completion in your own LMS or record system, so you can show who finished the course and when.

Yes, everything. Change the wording, swap scenarios for ones from your workplace, add your logo, or remove parts that don't apply.

Your own details, each highlighted inside the course:
  • Approved AI coding tools
  • AI pr label rule
  • Agent permissions standard
  • Appsec contact
  • Secure coding standard link
  • LMS or record system
Then edit anything else you like: wording, scenarios, your logo.
Visit the help centre (opens in a new tab)

Ready to run it?

Free. Copy the course, live deck and both surveys into your AhaSlides account in one click.

Claim the template