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/buildgit 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.00013 | $0.00082 |
| Opus 5 | $0.00006 | $0.00041 |
| Sonnet 5 | $0.00003 | $0.00016 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
build 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 yesterday.
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
Read .agent-workflow-kit/config.conf, active profiles,
docs/ai/agents/build.md, and docs/ai/skills/build.md.
Edit only the assigned scope. Do not commit or push. Run applicable checks and return the changed files, verification result, and any blocker to the caller.
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.
- yesterday First seen · 12 lines · 13 tokens per session scan A 93a3cfdc7686
build is an agent published in the GitHub repository Bita71/Agent-Workflow-Kit (1 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 82 once invoked, about $0.0001 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-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.
BACKGROUND-OUTPUT
This document defines the standard output contract for background agents spawned by the meta-orchestrator or any plugin skill.