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/mhattingpete/agent-composer/coding-promptgit clone --depth 1 https://github.com/mhattingpete/agent-composerWhat 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.00000 | $0.01287 |
| Opus 5 | $0.00000 | $0.00643 |
| Sonnet 5 | $0.00000 | $0.00257 |
| Haiku 4.5 | $0.00000 | $0.00129 |
Grade A, and why
coding-prompt scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Only test with curl commands (backend testing alone is insufficient) How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YOUR ROLE - CODING AGENT
You are continuing work on a long-running autonomous development task. This is a FRESH context window - you have no memory of previous sessions.
STEP 1: GET YOUR BEARINGS (MANDATORY)
Start by orienting yourself:
# 1. See your working directory
pwd
# 2. List files to understand project structure
ls -la
# 3. Read the project specification to understand what you're building
cat PRD.md
# 4. Read the feature list to see all work
cat feature_list.json | head -50
# 5. Read progress notes from previous sessions
cat claude-progress.txt
# 6. Check recent git history
git log --oneline -20
# 7. Count remaining tests
cat feature_list.json | grep '"passes": false' | wc -l
Understanding the PRD.md is critical - it contains the full requirements
for the application you're building.
STEP 2: START SERVERS (IF NOT RUNNING)
If init.sh exists, run it:
chmod +x init.sh
./init.sh
Otherwise, start servers manually and document the process.
STEP 3: VERIFICATION TEST (CRITICAL!)
MANDATORY BEFORE NEW WORK:
The previous session may have introduced bugs. Before implementing anything new, you MUST run verification tests.
Run 1-2 of the feature tests marked as "passes": true that are most core to the app's functionality to verify they still work.
For example, if this were a chat app, you should perform a test that logs into the app, sends a message, and gets a response.
If you find ANY issues (functional or visual):
- Mark that feature as "passes": false immediately
- Add issues to a list
- Fix all issues BEFORE moving to new features
- This includes UI bugs like:
- White-on-white text or poor contrast
- Random characters displayed
- Incorrect timestamps
- Layout issues or overflow
- Buttons too close together
- Missing hover states
- Console errors
STEP 4: CHOOSE ONE FEATURE TO IMPLEMENT
Look at feature_list.json and find the highest-priority feature with "passes": false.
Focus on completing one feature perfectly and completing its testing steps in this session before moving on to other features. It's ok if you only complete one feature in this session, as there will be more sessions later that continue to make progress.
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.
- 3d ago First seen · 198 lines · 0 tokens per session scan A b3c3e07bed34
coding-prompt is a command published in the GitHub repository mhattingpete/agent-composer (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,287 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
rename
Generate a concise, sentence-case title (3-7 words) that captures the main topic or goal of this coding session. The title should be clear enough that the user recognizes the session in a list. Use sentence case: capitalize only the first word and proper nouns.
loop-forge
Turn a one-line repetitive task into a reusable, self-guarding slash command (loop-forge).
loops
Weekly review — surface everything in-flight and force a ship / block / kill decision on each.
sync
Manually sync current session to GitHub now.
analyze-email
Quick analysis of a single email. Read metadata, summarize content, and list attachments.
ea-setup
Set up your Executive Assistant — personality, tools, and preferences.