write-instructions

write-instructions is a command for Claude Code, Cursor from AlexFischman/mcp-skill-creator-agency. It costs 0 tokens per session (834 once invoked), scanned A, original, MIT.

A guide for writing or refining instructions that control an AI agent's behaviour. It covers goals, context, examples, output formats, and tool use.

In plain words
What is it for?
Use it to draft or improve prompts for a role, workflow, tools, expected outputs, and edge cases.
Why use it?
It provides a structure for turning vague expectations into instructions an agent can follow more consistently.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md).

Good fit Use it to draft or improve prompts for a role, workflow, tools, expected outputs, and edge cases.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alexfischman/mcp-skill-creator-agency/write-instructions
Install

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.

Clone the repo
git clone --depth 1 https://github.com/AlexFischman/mcp-skill-creator-agency

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for write-instructions

README.md
[![agentmods](https://agentmods.dev/badge/commands/alexfischman/mcp-skill-creator-agency/write-instructions/github.svg)](https://agentmods.dev/commands/alexfischman/mcp-skill-creator-agency/write-instructions)
Your own site
<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.

agentmods 80×15 button for write-instructions

Your own site · 80×15
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 834 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00834
Opus 5 $0.00000 $0.00417
Sonnet 5 $0.00000 $0.00167
Haiku 4.5 $0.00000 $0.00083

Measured 9d ago against content hash f04a404b4754, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

.cursor/commands/write-instructions.md · 122 lines

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

  1. Start Simple: Use concise, verb-driven instructions
  2. Be Specific: Explicitly state desired outputs and formats
  3. Provide Examples: Include concrete examples of expected behavior
  4. Use Positive Instructions: "Do this" rather than "Don't do that"
  5. Integrate Tools: Show exactly when and how to use each tool
  6. Test Your Own Writing: Think about how you would react to the instructions you're writing
  7. 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.md FIRST

Step 2: Ask the User Key Questions

Read the full file on GitHub · 122 lines

Changes

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.

  1. 9d ago First seen · 122 lines · 0 tokens per session scan A f04a404b4754

Subscribe to this mod's changes

write-instructions is a command published in the GitHub repository AlexFischman/mcp-skill-creator-agency (2 stars, last pushed 9mo 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.