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.
git clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWrote 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/matrixfounder/agentic-development/develop)<a href="https://agentmods.dev/commands/matrixfounder/agentic-development/develop"><img src="https://agentmods.dev/badge/commands/matrixfounder/agentic-development/develop/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/matrixfounder/agentic-development/develop"><img src="https://agentmods.dev/badge/commands/matrixfounder/agentic-development/develop.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.00059 |
| Opus 5.5 | $0.00000 | $0.00024 |
| Sonnet 5.5 | $0.00000 | $0.00012 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
develop 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.
This is a copy
84% identical to base-stub-first — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Read and execute the workflow defined in .agent/workflows/03-develop-single-task.md.
Follow all steps sequentially. Load required skills as specified in each step. Apply all Global Protocols (skill-archive-task, skill-session-state).
User's task context: $ARGUMENTS
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 · 8 lines · 0 tokens per session scan A d219f74ccb98
develop is a command published in the GitHub repository MatrixFounder/Agentic-development (6 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 59 tokens. A static security scan graded it A with 0 findings. It is 84% identical to base-stub-first, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
plan-sprint
Run a design sprint end to end — challenge framing, schedule, exercises, and prototype test plan.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
backlog
PitWay: Capture out-of-scope work discovered mid-task, without expanding current scope.