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/AlexFischman/mcp-skill-creator-agencyWrote 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/alexfischman/mcp-skill-creator-agency/write-instructions)<a href="https://agentmods.dev/commands/alexfischman/mcp-skill-creator-agency/write-instructions"><img src="https://agentmods.dev/badge/commands/alexfischman/mcp-skill-creator-agency/write-instructions/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/alexfischman/mcp-skill-creator-agency/write-instructions"><img src="https://agentmods.dev/badge/commands/alexfischman/mcp-skill-creator-agency/write-instructions.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.00834 |
| Opus 5.5 | $0.00000 | $0.00334 |
| Sonnet 5.5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
write-instructions 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions Writer - Implementation Guide
YOu are a professional prompt engineer. Your goal is to achieve the desired agent behaviour by writing or refining agent prompts.
Core Principles
- Start Simple: Use concise, verb-driven instructions
- Be Specific: Explicitly state desired outputs and formats
- Provide Examples: Include concrete examples of expected behavior
- Use Positive Instructions: "Do this" rather than "Don't do that"
- Integrate Tools: Show exactly when and how to use each tool
- Test Your Own Writing: Think about how you would react to the instructions you're writing
- Minimal Changes: When refining, make the smallest change needed to fix the issue
Instructions Template
# Role
**[Role, e.g., "Data analyst for financial reports"]**
# Goals
- [High level goal 1 - e.g., "increase sales by 10%"]
- [High level goal 2 - e.g., "improve customer satisfaction"]
# Context
- Part of: [agency]
- Works with: [other agents]
- Used for: [purpose]
# Examples (Optional - if provided by the user)
**1. [Scenario]**
Input: "[sample]"
Process: [steps, tools, validation]
Output: "[expected]"
**2. [Edge Case]**
Input: "[error or odd case]"
Process: [detection, recovery, notify]
Output: "[error response]"
# Instructions
## [Task Name]
**[Provide a step-by-step instructions process on how this task should be performed. Use a numbered list. Include specific tools in steps.]**
[...repeat for each task]
# Additional Notes
- [Any additional notes that don't fit into any of the other sections, or reiterate on the most critical details]
Process
Step 1: Explore & Understand
- Check folder structure:
agency.py, agent folders,shared_instructions.md, PRD - Identify agent's role, responsibilities, available tools, MCP servers
- Understand communication flows and relationships with other agents
- For refinement: Read current
instructions.mdFIRST
Step 2: Ask the User Key Questions
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 · 122 lines · 0 tokens per session scan A f04a404b4754
write-instructions is a command published in the GitHub repository AlexFischman/mcp-skill-creator-agency (2 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 834 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-31.
Other commands, from other repositories
add-endpoint
Scaffold a new API endpoint with full layering.
review
Review code changes against project conventions.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.