Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add arozumenko/sdlc-skills --skill security-engagementgit clone --depth 1 https://github.com/arozumenko/sdlc-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/arozumenko/sdlc-skills/security-engagement)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/security-engagement"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/security-engagement/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/security-engagement"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/security-engagement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00054 | $0.00750 |
| Opus 5.5 | $0.00022 | $0.00300 |
| Sonnet 5.5 | $0.00011 | $0.00150 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
security-engagement scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security engagement
You are the lead. This skill has no scripts of its own — it is the
procedure that sequences secure-code-review, threat-modeling,
security-test-planning and risk-register, and the dispatches to
security-reviewer and threat-modeler in between. You run the row
verbs and the read-only commands yourself; the emitter-only events
(fixed, regressed, acceptance-expired) are appended by the
scripts, never typed by you.
The one procedure
references/workflow.md is the only place the 11-step operator
flow lives — one fenced command per step, with the result line that
tells you it worked. Do not restate the steps elsewhere; point at this
file. In brief: start the engagement, dispatch the review, check it,
get second opinions where warranted, register the verified findings,
dispatch the threat model, admit and hand off the candidate cases,
report, verify fixes, record acceptances, sign off.
References
references/workflow.md— the 11 steps, in spec §7 order, each a fenced command plus its expected result line.references/sign-off-checklist.md— spec §7 step 11 in full: the four checks (cite.mjs checkon findings and on the threat model,cases.mjs verify-suite,register.mjs statusplus a cleangit status), what "OK" lets you say, and what to hand over.references/tracker-rules.md— filing a finding: search first throughissue-tracking, post, thenregister.mjs ticket <R-id> <url>. Threats are not ticketed in v1.
Standalone vs factory install
Installed alone (--skills security-testing/security-engagement), this
skill still expects the sibling skills — secure-code-review,
threat-modeling, security-test-planning, risk-register — to be
installed too; it names their scripts by relative path
(../secure-code-review/scripts/cite.mjs, and so on) rather than
shipping copies. Install the whole security-testing factory
(--factory security-testing) to get the lead role, the specialist
agents, and all five skills together with one engagement.md shared
across them. REGISTER: skipped (risk-register not installed) from
verify.mjs, and no register.mjs/cases.mjs commands to run in
references/workflow.md, are what a secure-code-review-only install
looks like — this skill is not that install.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 65 lines · 54 tokens per session scan A 3adc1be45e5a
security-engagement is a skill published in the GitHub repository arozumenko/sdlc-skills (25 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 750 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-19.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.