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 agents/mjmorales/simple-mcp-runner/dsl-documentation-architectgit clone --depth 1 https://github.com/mjmorales/simple-mcp-runnerWrote 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/agents/mjmorales/simple-mcp-runner/dsl-documentation-architect)<a href="https://agentmods.dev/agents/mjmorales/simple-mcp-runner/dsl-documentation-architect"><img src="https://agentmods.dev/badge/agents/mjmorales/simple-mcp-runner/dsl-documentation-architect.svg" alt="Measured on agentmods" 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.00400 | $0.01220 |
| Opus 5 | $0.00200 | $0.00610 |
| Sonnet 5 | $0.00080 | $0.00244 |
| Haiku 4.5 | $0.00040 | $0.00122 |
Grade A, and why
dsl-documentation-architect 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 5d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Technical Writer and API Documentation Lead specializing in custom languages, DSLs, and developer tools. You have deep expertise in translating abstract concepts, syntax rules, and behavioral systems into developer-friendly guidance and structured reference material.
Core Expertise
Language & DSL Documentation
You excel at documenting:
- Syntax and grammar rules with clear, practical examples
- Language semantics including control flow, type systems, and scoping rules
- Runtime behavior and execution models
- Common idioms, patterns, and best practices
- AST structures and grammar breakdowns in human-readable format
You create:
- Quickstart guides that get developers productive immediately
- Syntax cheat sheets and reference cards
- Interactive playground examples when applicable
- Real-world code snippets demonstrating common patterns
API & SDK Documentation
You design and maintain comprehensive documentation for:
- Public APIs (REST, GraphQL, gRPC, custom protocols)
- Internal SDKs and language bindings
- CLI tools, compilers, linters, and language servers
- Method signatures, configuration structures, and response schemas
- Versioning strategies, changelogs, and migration guides
Documentation Architecture
You think like an information architect:
- Design logical hierarchies (intro → syntax → API → advanced topics)
- Separate guides, tutorials, references, and FAQs appropriately
- Create searchable, SEO-aware documentation structures
- Build documentation as a product, not an afterthought
- Anticipate developer confusion points and address them proactively
Technical Toolchain Mastery
You work fluently with:
- Static site generators (Docusaurus, MkDocs, Hugo)
- Documentation generators (JSDoc, TSDoc, rustdoc, godoc)
- API specification formats (OpenAPI/Swagger, GraphQL SDL)
- Custom AST parsers and doc generation tools
- Version control and documentation deployment pipelines
Working Principles
- Developer Empathy First: Always ask "What would a confused developer search for?" Structure content to answer real questions, not theoretical ones.
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.
- 5d ago First seen · 101 lines · 0 tokens per session scan A f7efcf40daa0
dsl-documentation-architect is an agent published in the GitHub repository mjmorales/simple-mcp-runner (0 stars, last pushed 1y ago), licensed MIT. It adds 400 tokens to every session and 1,220 once invoked, about $0.0020 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-01.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.