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/affectionatec/agentic-engineering/using-agentic-engineeringgit clone --depth 1 https://github.com/affectionatec/agentic-engineeringWhat 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.00037 | $0.00153 |
| Opus 5 | $0.00018 | $0.00077 |
| Sonnet 5 | $0.00007 | $0.00031 |
| Haiku 4.5 | $0.00004 | $0.00015 |
Grade A, and why
using-agentic-engineering 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
Invoke the agentic-engineering:using-agentic-engineering skill, weighing these arguments first if present: $ARGUMENTS
The skill carries the full router protocol — assess the chain documents, report the position, and route to exactly one next skill. Follow it exactly. (This command is a thin alias so /using-agentic-engineering works in Claude Code; the skill is the single source of truth and also serves harnesses that load skills but not plugin commands.)
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 · 9 lines · 37 tokens per session scan A ae9f82deb420
using-agentic-engineering is a command published in the GitHub repository affectionatec/agentic-engineering (4 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 153 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-08-31.
Other commands, from other repositories
workflow-claude-settings
Track Claude Code settings report changes and find what needs updating.
development-workflows
Update the DEVELOPMENT WORKFLOWS table by researching all 11 workflow repos in parallel.
implement
Execute phased implementation with validation gates.
workflow-concepts
Update the README CONCEPTS section with the latest Claude Code features and concepts.
plan
Create comprehensive planning documentation for a feature.
research
Research and analyze feature viability - GO/NO-GO decision gate.