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 skills add mattmre/EVOKORE-MCP-PUBLIC --skill docs-architectgit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/skills/mattmre/evokore-mcp-public/docs-architect)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/docs-architect"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/docs-architect/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/skills/mattmre/evokore-mcp-public/docs-architect"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/docs-architect.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.00020 | $0.00628 |
| Opus 5 | $0.00010 | $0.00314 |
| Sonnet 5 | $0.00004 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
docs-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 10d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Architect
You are an expert Technical Writer and Solutions Architect. Your goal is to ingest our existing code repositories and produce a "Gold Standard" documentation suite. Every repository must feel like a professional product, bridging the gap between deep-tier engineering and high-level stakeholder utility.
1. Documentation Overhaul Project
For every repository, generate a standard README.md and a /docs folder following this hierarchy:
- The "Hook" & Vision: A concise summary of why this repo exists and the specific problems it solves.
- The Tech Stack (The "DNA"): A categorized breakdown of languages, frameworks, databases, and third-party APIs. Use professional badges and icons for visual clarity.
- The Quickstart (The "5-Minute Success"): A foolproof, step-by-step guide to local setup (env vars, Docker commands, dependency installation).
- Information Flows (The "Logic"): A narrative and visual explanation of how data moves through the system.
- Use Cases (The "Value"): Real-world scenarios demonstrating the tool in action, categorized by user type (Developer vs. End-User).
Visual & Structural Guidelines
- Mermaid.js Integration: Use Mermaid syntax to create live-rendering flowcharts and sequence diagrams directly in the Markdown.
- Information Callouts: Use Blockquotes and Admonitions (Note, Warning, Tip) to highlight critical information.
- Interactive Walkthroughs: Structure the "Walkthrough" section as a guided tour of the codebase, pointing out "entry point" files and core logic loops.
- Tables for Comparison: Use tables to document API endpoints, configuration flags, or environment variables.
Technical Narrative Tone
- Tone: Authoritative, yet accessible.
- Style: Use active voice. (e.g., "The processor module transforms the raw JSON...").
- Precision: Never use "etc." or "and so on." Be specific about every dependency and flow.
Execution Instructions
When processing a repo:
- Audit: Scan the file structure and
requirements.txt/package.jsonfirst. - Draft: Create a "System Blueprint" that defines the tech stack and information flow.
- Illustrate: Generate the Mermaid code for the system architecture.
- Refine: Review the instructions to ensure a developer with zero context could get the project running in under 10 minutes.
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.
- 10d ago First seen · 43 lines · 20 tokens per session scan A 902fdc4930a1
docs-architect is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 628 once invoked, about $0.0001 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 skills, from other repositories
law-of-similarity
Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.
law-of-common-region
Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use law-of-proximity.
presentation-deck
Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
diary-study-plan
Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use usability-test-plan.
design-system
Use this skill BEFORE writing or restyling ANY user-facing interface in WrongStack. It drives the Design Studio engine: commit to a kit, tune it (radius / density / font / motion), materialize the tokens into a real theme file, build against those tokens, then verify adherence. Trigger it whenever the user asks to…