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 agents/bita71/agent-workflow-kit/review-securitygit clone --depth 1 https://github.com/Bita71/Agent-Workflow-KitWhat 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 | $0.00000 | $0.00072 |
| Opus 5 | $0.00000 | $0.00036 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
review-security 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.
What it actually says
Review Security
Read docs/ai/skills/review-security.md and perform the security review strictly by it.
Context: run only when the codex review orchestrator passes a security-sensitive diff or the user explicitly asks for a security review. If no file list is passed, determine the changed files via git diff --name-only.
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 · 6 lines · 0 tokens per session scan A 49d67d9a90c8
review-security is an agent published in the GitHub repository Bita71/Agent-Workflow-Kit (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 72 tokens. 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-08-31.
Other agents, from other repositories
intelligence-architect
Design and prune the intelligence layer - rule vs skill vs agent, split what grew, remove duplication and hardcoded paths.
intelligence-operator
Run the engine's mechanical flows - sync, update, adapter install and removal.
code-reviewer
Use after completing a step or batch of implementation work. Reviews against the HOTL workflow and HOTL contracts. Flags BLOCK/WARN/NOTE issues with file:line references.
qa-agent
Name: qa-agent Role: Automated Quality Assurance & Test Generation Trigger: After any code generation or modification by a coding agent.
meta-orchestrator
Master agent coordinating all tools, MCPs, agents, and skills. Plans multi-system workflows by chaining MCPs, spawning specialized agents, and using Computer Use for native apps.
incident-responder
Sentry-triggered incident response agent. Reads error events, traces to source code, proposes fixes, creates branches, and opens PRs with the fix.