Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install security-assessmentWrote 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/commands/bdfinst/agentic-dev-team/security-assessment)<a href="https://agentmods.dev/commands/bdfinst/agentic-dev-team/security-assessment"><img src="https://agentmods.dev/badge/commands/bdfinst/agentic-dev-team/security-assessment.svg" alt="Measured on agentmods" 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.00044 | $0.01315 |
| Opus 5 | $0.00022 | $0.00658 |
| Sonnet 5 | $0.00009 | $0.00263 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
security-assessment 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 2d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/security-assessment
Orchestrator for the static-analysis pipeline. Execute the phase graph
defined in skills/security-assessment-pipeline/SKILL.md. Phases dispatch
to agents/scripts; artifacts pass through memory/. Produces a
publication-ready exec report per target (plus a cross-repo summary for
multi-target runs).
Constraints
- Follow the pipeline exactly. The skill is authoritative. Do not reorder phases or skip deterministic gates.
- Never silently drop findings. Every input flows through to either the published report or a suppression appendix with reason.
- Artifacts are the source of truth. Every phase writes to
memory/;--startand failure-recovery rely on that. - Informational-not-audit-grade. Every produced report carries the
compliance disclaimer (verbatim per
knowledge/disclaimers.md) at the header.
Parse arguments
Arguments: $ARGUMENTS
Positional: one or more directory paths (target repos).
Flags:
--start <phase>: resume from phase (0 / 1 / 1b / 2 / 3 / 4 / 5). Requires prior phase artifacts inmemory/.--agents <phase> [<phase> ...]: run only listed phases. Dependency check skipped.--fp-reduce=yes|no: skip Phase 2 FP-reduction whenno. Defaultyes.
Steps
1. Validate arguments
- ≥ 1 target path required.
- Each target must be a directory (not a file).
- For each target: consult
ACCEPTED-RISKS.mdif present at the target root.
2. Initialize run
For each target repo, derive a slug from the directory name (kebab-cased, lowercased). Multi-repo runs use dash-joined slug for cross-repo artifacts.
Create memory/audit-<slug>.jsonl (append-only). Record run start with
targets, flags, and contract version. If prior artifacts exist AND
--start is NOT set, archive them to memory/archive/<timestamp>/
before overwriting.
3. Execute the phase graph
Follow skills/security-assessment-pipeline/SKILL.md § "Phase graph".
The skill defines per-phase inputs, outputs, agents/scripts, and
parallelism. Three parallelism rules MUST be observed:
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.
- 2d ago First seen · 136 lines · 44 tokens per session scan A 40db503b0de1
security-assessment is a command published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 1,315 once invoked, about $0.0002 per session on Opus 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-05.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.