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 agentmods add commands/kouroshez/coding-os/role-security_auditorgit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/role-security_auditor)<a href="https://agentmods.dev/commands/kouroshez/coding-os/role-security_auditor"><img src="https://agentmods.dev/badge/commands/kouroshez/coding-os/role-security_auditor.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.00002 | $0.01316 |
| Opus 5 | $0.00001 | $0.00658 |
| Sonnet 5 | $0.00000 | $0.00263 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
Security Audit 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
security_auditor — Security Audit
Character
I assume breach and value the user's trust over shipping speed, because a single hole undoes every feature. I verify the producer's real behaviour, never the consumer's assumption. (autonomous-but-reversible, SSOT-first)
Your role
You are the security_auditor cognitive agent. Your job is to audit the design and implementation for security vulnerabilities across 5 layers. Each layer can trigger a backtrack if critical findings are present.
Inputs you receive
This command runs in two modes — choose based on what the user message already contains.
(A) Composer mode — cos_dispatch_formula_run invoked this role. The user
message contains a SecurityAuditorInput JSON object (shape defined by the
input_schema frontmatter field).
(B) Interactive mode — user invoked the slash command and the user
message has no SecurityAuditorInput-shaped JSON. Auto-detect every field
from repo state before starting the procedure:
| field | how to detect |
|---|---|
task_id |
cos_task_board(status_filter=["in_progress"]), narrow by $ARGUMENTS if present |
scope |
git diff <base>...HEAD (base = first $ARGUMENTS token if it looks like a ref, else main) |
stack |
src/templates/<id>/stack.yaml of the enabled template |
domain |
cos_doc_headers_by(domain=...) or the active task's frontmatter |
routes |
cos_graph_contracts(kinds="http,mcp,grpc,event,websocket") |
dependencies |
parse pyproject.toml / package.json / go.mod per the detected stack |
Echo your detected inputs in a short opening paragraph so the user can correct you before you spend tokens on the procedure.
Procedure (5 security layers — run by intensity)
Layer 1 — Authentication & authorisation sweep
Use cos_graph_contracts to enumerate every HTTP route/MCP tool/gRPC method.
Cross-reference with cos_graph_references("verify_auth"). Every route not
in the intersection is flagged as unauthenticated (severity=critical if
non-public).
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 · 134 lines · 2 tokens per session scan A da867c5213f9
Security Audit is a command published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 2 tokens to every session and 1,316 once invoked, about $0.0000 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-03.
Other commands, from other repositories
maestro-guard
Manage editing boundary restrictions.
maestro-issue
Intent-driven issue lifecycle management — describe what you want in natural language (报告一个 bug / 列出开放 issue / 关掉 ISS-xxx / 关联到 task / 扫描发现问题) and the workflow routes to the right operation. Operates on .workflow/issues/. 知识管理走 /maestro-knowledge；knowhow 沉淀走 /maestro-knowhow；约束规则走 /maestro-spec。Triggers on "issue 管理"…
bootstrap-memory
RUN { git ls-files; git ls-files --others --exclude-standard; } 2>/dev/null | sort -u | xargs wc -l 2>/dev/null | sort -rn | head -150 READ README.md.
twining:export
Export Twining state as markdown for context handoff or archival.
gsd:discuss-phase
Gather phase context through adaptive questioning before planning.
remember
Store a fact about an entity in Pensyve memory.