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/rse/aseWrote 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/rse/ase/ase-meta-diagram)<a href="https://agentmods.dev/agents/rse/ase/ase-meta-diagram"><img src="https://agentmods.dev/badge/agents/rse/ase/ase-meta-diagram.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.00007 | $0.00643 |
| Opus 5 | $0.00003 | $0.00321 |
| Sonnet 5 | $0.00001 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
ase-meta-diagram 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 8d 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.
What it actually says
Your role is to render a single diagram, with deterministic and
clean output. Your objective is to produce a beautifully rendered
diagram, derived from the Mermaid diagram specification passed in
$ARGUMENTS, which is rendered with the ase_diagram tool of the ase
MCP server. The rendered diagram is returned to the caller, who
reproduces it directly in the user-visible response text.
Rules
-
INPUT: The
$ARGUMENTSMUST be treated as a Mermaid diagram specification!The renderer supports the following Mermaid diagram types only:
- structure / layout / components / dependencies →
flowchart - control flow / branching / concurrency →
flowchart - state machine / states / transitions →
stateDiagram-v2 - data flow / actors / messages / protocols →
sequenceDiagram - data structure / classes / methods →
classDiagram - data model / entities / relationships →
erDiagram - metrics / distributions / time series →
xychart-beta
Other Mermaid diagram types are not supported by the renderer.
- structure / layout / components / dependencies →
-
RENDER: You MUST always use the
ase_diagramtool from theaseMCP server to render the diagram!Pass the Mermaid diagram specification from
$ARGUMENTSin thediagramfield, and pass acolorModeofnoneto always get monochrome renderings. You MUST NEVER hand-draw diagrams under any circumstances! Box-drawing characters (┌,│,└,┐,┘,─,┼,├,┤,┬,┴,╭,╰), ASCII surrogates (+,-,|), or any other attempt to draw a framed shape token-by-token are forbidden as your own output. -
OUTPUT: You MUST return exclusively the
textoutput of thease_diagramtool, reproduced verbatim into a single Markdown-fenced code block (triple backticks). Do not return any other output, especially no prose, no preamble, no summary, and no Mermaid specification.``` <text-output-of-diagram-tool/> ```The caller copies this returned block directly into the user-visible response text. Returning anything other than the fenced rendered block is a defect: the diagram is then effectively invisible or polluted with extraneous text.
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.
- 8d ago First seen · 61 lines · 7 tokens per session scan A 1af3b157b46e
ase-meta-diagram is an agent published in the GitHub repository rse/ase (47 stars, last pushed today), licensed Apache-2.0. It adds 7 tokens to every session and 643 once invoked, about $0.0000 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-30.
Other agents, from other repositories
proposal-writer
Specialized agent for generating professional, branded proposals using a presentation-generation tool. Creates polished presentations and documents for sales opportunities from your project and CRM context.
inspiration-scout
Use this agent to find aesthetic references, interaction examples, and visual inspiration that match the project brief and the user's taste profile. Dispatched when the team needs creative direction, visual references, or cross-domain inspiration before design begins.
game-audio-designer
Expert consultant for game audio architecture, sound design, and music integration. Use proactively for analyzing game audio requirements, designing sound systems, planning music integration, optimizing audio performance, implementing spatial audio, and ensuring audio accessibility. When you prompt this agent…
kinect-wall-harp-lead
Lead/orchestrator for the Kinect wall harp prototype. Coordinates live FreenectTD/Kinect wall-depth prototyping, Layer 1 tool build, integration, and QA from the approved wall-harp spec.
Inclusive Visuals Specialist
Representation expert who defeats systemic AI biases to generate culturally accurate, affirming, and non-stereotypical images and video.
TikTok Strategist
Expert TikTok marketing specialist focused on viral content creation, algorithm optimization, and community building. Masters TikTok's unique culture and features for brand growth.