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 shrimbly/project-wiki --skill wiki-diagramgit clone --depth 1 https://github.com/shrimbly/project-wikiWrote 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/shrimbly/project-wiki/wiki-diagram)<a href="https://agentmods.dev/skills/shrimbly/project-wiki/wiki-diagram"><img src="https://agentmods.dev/badge/skills/shrimbly/project-wiki/wiki-diagram/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/shrimbly/project-wiki/wiki-diagram"><img src="https://agentmods.dev/badge/skills/shrimbly/project-wiki/wiki-diagram.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.00088 | $0.01132 |
| Opus 5 | $0.00044 | $0.00566 |
| Sonnet 5 | $0.00018 | $0.00226 |
| Haiku 4.5 | $0.00009 | $0.00113 |
Grade A, and why
wiki-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 12d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki-diagram
Add or refresh a visual for the wiki. Don't assume an entity diagram — the right
kind of diagram depends on what the project is about, so understand it first, then let
the user pick the type. The viewer renders ```mermaid blocks, so diagrams live as
markdown in wiki/diagrams/.
1. Understand the project first
Read wiki/index.md and wiki/overview.md, and skim what the wiki actually contains
— wiki/entities/, wiki/concepts/, wiki/decisions/, any flow/persona pages, and
existing wiki/diagrams/. You're working out what this project really models (a
data/domain model? a set of user flows? an execution pipeline? a system architecture?
a lifecycle?) so the options you offer are grounded in the material, not generic.
If the user already named the diagram they want (or asked to refresh a specific one), skip to step 3.
2. Ask what kind of diagram (interactive)
Propose the 3–4 diagram types that actually fit this project's material and let the
user choose with AskUserQuestion (recommend the best fit first; they can pick
"Other"). Ground each option in the project — name the entities/flows it would show,
not just the abstract type ("a user-flow diagram of the freelancer install-gate path",
not "a flowchart"). Common types:
| Type | Shows | Good when the wiki has… | Mermaid |
|---|---|---|---|
| Entity / relationship | the nouns and how they connect | rich entities/, containment/ownership |
graph TD or erDiagram |
| User flow / journey | the steps a persona takes to reach a goal | personas, flows, UX content | flowchart LR or journey |
| Sequence | interactions between actors/components over time | execution, protocols, APIs, request paths | sequenceDiagram |
| State / lifecycle | the states of a thing and its transitions | status fields, lifecycles, approvals | stateDiagram-v2 |
| Architecture / system | components, layers, and boundaries | services, local/cloud split, integrations | flowchart with subgraphs |
| Concept map | how ideas relate (looser than a data model) | concept-heavy, few hard entities | graph or mindmap |
| Timeline / roadmap | phases or milestones over time | roadmaps, staged rollouts | timeline or gantt |
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.
- 12d ago First seen · 103 lines · 88 tokens per session scan A 6ff1daf14fd8
wiki-diagram is a skill published in the GitHub repository shrimbly/project-wiki (5 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,132 once invoked, about $0.0004 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
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
make-resume
A Chinese-language tool for creating editable HTML resumes that can be changed in a browser and printed to PDF. It uses available resume templates when they are installed and otherwise provides a simpler fallback.