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/imMamdouhaboammar/marketing-council-packWrote 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/immamdouhaboammar/marketing-council-pack/feature-development)<a href="https://agentmods.dev/commands/immamdouhaboammar/marketing-council-pack/feature-development"><img src="https://agentmods.dev/badge/commands/immamdouhaboammar/marketing-council-pack/feature-development/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/immamdouhaboammar/marketing-council-pack/feature-development"><img src="https://agentmods.dev/badge/commands/immamdouhaboammar/marketing-council-pack/feature-development.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.00016 | $0.00183 |
| Opus 5 | $0.00008 | $0.00092 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
feature-development 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 7d 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
/feature-development
Use this workflow when working on feature-development in marketing-council-pack.
Goal
Standard feature implementation workflow
Common Files
**/api/**
Suggested Sequence
- Understand the current state and failure mode before editing.
- Make the smallest coherent change that satisfies the workflow goal.
- Run the most relevant verification for touched files.
- Summarize what changed and what still needs review.
Typical Commit Signals
- Add feature implementation
- Add tests for feature
- Update documentation
Notes
- Treat this as a scaffold, not a hard-coded script.
- Update the command if the workflow evolves materially.
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.
- 7d ago First seen · 35 lines · 16 tokens per session scan A 65594c0001a2
feature-development is a command published in the GitHub repository imMamdouhaboammar/marketing-council-pack (4 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 183 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-09-03.
Other commands, from other repositories
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
rust-test
Enforce TDD workflow for Rust. Write tests first, then implement. Verify 80%+ coverage with cargo-llvm-cov.
tdd
Legacy slash-entry shim for the tdd-workflow skill. Prefer the skill directly.
god-mode
GOD mode — the constructive crew. Recalls past solutions, designs, builds test-first, self-critiques, hardens, and proves the work with a command that actually runs.
refactor-sprint
Parallel refactor sprint — fires refactor-cleaner + code-simplifier + type-design-analyzer + tdd-guide simultaneously. Full cleanup in one pass.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.