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 instructions/ssdeanx/ssd-ai/markdowngit clone --depth 1 https://github.com/ssdeanx/ssd-aiWhat 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.00725 | $0.00725 |
| Opus 5 | $0.00362 | $0.00362 |
| Sonnet 5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
ssd-ai markdown.instructions.md 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- my-awesome-copilot markdown.instructions.md — 100% identical, 1 lines differ
- github-copilot-instructions markdown.instructions.md — 94% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Content Rules
The following markdown content rules are enforced in the validators:
- Headings: Use appropriate heading levels (H2, H3, etc.) to structure your content. Do not use an H1 heading, as this will be generated based on the title.
- Lists: Use bullet points or numbered lists for lists. Ensure proper indentation and spacing.
- Code Blocks: Use fenced code blocks for code snippets. Specify the language for syntax highlighting.
- Links: Use proper markdown syntax for links. Ensure that links are valid and accessible.
- Images: Use proper markdown syntax for images. Include alt text for accessibility.
- Tables: Use markdown tables for tabular data. Ensure proper formatting and alignment.
- Line Length: Limit line length to 400 characters for readability.
- Whitespace: Use appropriate whitespace to separate sections and improve readability.
- Front Matter: Include YAML front matter at the beginning of the file with required metadata fields.
Formatting and Structure
Follow these guidelines for formatting and structuring your markdown content:
- Headings: Use
##for H2 and###for H3. Ensure that headings are used in a hierarchical manner. Recommend restructuring if content includes H4, and more strongly recommend for H5. - Lists: Use
-for bullet points and1.for numbered lists. Indent nested lists with two spaces. - Code Blocks: Use triple backticks (
) to create fenced code blocks. Specify the language after the opening backticks for syntax highlighting (e.g.,csharp). - Links: Use
[link text](URL)for links. Ensure that the link text is descriptive and the URL is valid. - Images: Use
for images. Include a brief description of the image in the alt text. - Tables: Use
|to create tables. Ensure that columns are properly aligned and headers are included. - Line Length: Break lines at 80 characters to improve readability. Use soft line breaks for long paragraphs.
- Whitespace: Use blank lines to separate sections and improve readability. Avoid excessive whitespace.
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.
- 2d ago First seen · 53 lines · 725 tokens per session scan A c8a18705593e
ssd-ai markdown.instructions.md is an instructions file published in the GitHub repository ssdeanx/ssd-ai (3 stars, last pushed 8mo ago), licensed MIT. It adds 725 tokens to every session, about $0.0036 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-08-31.
Other instructions, from other repositories
Genesis-World-MCP AGENTS.md
AGENTS.md instructions for Gnidreve/Genesis-World-MCP, covering agents.md — cas genesisworld mcp, what this is, standing orders — read first, design pillars and source layout & conventions.
atelier-mcp copilot-instructions.md
Copilot instructions for anshrajore/atelier-mcp, covering run npm run sync-adapters to update, universal ui/ux rules, universal backend architecture rules and framework presets (available in skills/atelier/presets/).
atelier-mcp CLAUDE.md
Claude Code instructions for anshrajore/atelier-mcp, covering atelier quality gate adapter for claude code (claude.md), run npm run sync-adapters to update, universal ui/ux rules, universal backend architecture rules and framework presets (available in skills/atelier/presets/).
atelier-mcp AGENTS.md
AGENTS.md instructions for anshrajore/atelier-mcp, covering atelier quality gate adapter for agents.md, run npm run sync-adapters to update, universal ui/ux rules, universal backend architecture rules and framework presets (available in skills/atelier/presets/).
mcpscore AGENTS.md
Instructions for mcp-box/mcpscore, covering agent instructions for mcpscore and gotchas (learned the hard way).
mcp-scribe CLAUDE.md
Instructions for The-Swarm-Corporation/mcp-scribe, covering claude.md, what this is, commands, formatting: black only. do not run ruff format and architecture.