Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JeremyDev87/codingbuddynpx agentmods add commands/jeremydev87/codingbuddy/actWrote 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/jeremydev87/codingbuddy/act)<a href="https://agentmods.dev/commands/jeremydev87/codingbuddy/act"><img src="https://agentmods.dev/badge/commands/jeremydev87/codingbuddy/act/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jeremydev87/codingbuddy/act"><img src="https://agentmods.dev/badge/commands/jeremydev87/codingbuddy/act.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01857 |
| Opus 5.5 | $0.00000 | $0.00743 |
| Sonnet 5.5 | $0.00000 | $0.00371 |
| Haiku 4.5 | $0.00000 | $0.00186 |
Grade A, and why
act 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 1mo 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACT Mode
Purpose
Execute the implementation plan with TDD
Mode Availability
Standalone Mode (no MCP server)
This command works without the CodingBuddy MCP server. In standalone mode, you get:
- Mode detection and transition
- TDD cycle execution (Red → Green → Refactor)
- Basic quality standards enforcement
- Agent-guided implementation
MCP Enhanced Mode
With the CodingBuddy MCP server connected, you additionally get:
parse_modewith full context tracking- Specialist agent dispatch for implementation verification
- Contextual checklists (security, accessibility, performance)
- Cross-session context persistence
Activation
Invoke via /codingbuddy:act (namespaced) or the ACT keyword.
Legacy bare
/actis deprecated. See Migration Guide.
This command activates ACT mode for the CodingBuddy workflow.
Instructions
Important:
- ACT mode executes the plan created in PLAN mode
- After ACT completes, automatically return to PLAN mode (default behavior)
- User can request EVAL for quality assessment
Trigger:
- Type
ACTafter PLAN is ready - Execute implementation steps defined in PLAN
🔴 Agent Activation (STRICT):
- When ACT is triggered, the default ACT agent (loaded via parse_mode in MCP mode; Software Engineer in standalone mode) MUST be automatically activated
- The Agent's development philosophy and code quality checklist MUST be followed
- In MCP mode, the agent framework is loaded via parse_mode. In standalone mode, basic workflow guidance is provided by the mode detection hook.
Purpose: Execute implementation following TDD cycle, augmented coding principles, and quality standards
What ACT does (with Software Engineer):
- Execute TDD Cycle (via Software Engineer)
- 🔴 For core logic: Red → Green → Refactor cycle
- Write failing test first
- Implement minimal code to pass
- Refactor only after tests pass
- 🔴 Required: Follow Software Engineer's TDD cycle
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.
- 1mo ago First seen · 218 lines · 0 tokens per session scan A 8987790d058d
act is a command published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,857 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-30.
Other commands, from other repositories
forge
/forge Full Forge pipeline (semi-auto + parallel) /forge [prd-file] Forge a specific PRD /forge --blitz Forge with TDD enforcement.
refactor
You are the Refactor Specialist, a rigorous code quality engineer who improves code structure, maintainability, and performance while preserving behavior. You never break working code - you make it better.
blitz
/blitz is a thin alias for /go --mode=semi-auto --parallel --tdd. It runs the full /go pipeline at maximum speed: semi-auto remediation + parallel wave execution + TDD enforcement. Blitz is for well-defined PRDs with independent stories.
config
Complete configuration guide for pair programming sessions.
start
Start a new pair programming session with AI assistance.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.