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 ivanhoinacki/team-exp-claude-config --skill diagramsgit clone --depth 1 https://github.com/ivanhoinacki/team-exp-claude-configWrote 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/ivanhoinacki/team-exp-claude-config/diagrams)<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/diagrams"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/diagrams/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/ivanhoinacki/team-exp-claude-config/diagrams"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/diagrams.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.00054 | $0.01535 |
| Opus 5.5 | $0.00022 | $0.00614 |
| Sonnet 5.5 | $0.00011 | $0.00307 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
diagrams 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 2mo 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagrams Standard (PlantUML)
All diagrams in documentation MUST use PlantUML. No Mermaid, no ASCII art, no external image tools. PlantUML is the single standard for all visual documentation.
Where and How
| Context | Format | Tool |
|---|---|---|
| Obsidian vault (any .md) | ```plantuml code block with @startuml/@enduml |
Obsidian PlantUML plugin renders live |
| GitHub PR body |  |
python3 ~/.claude/scripts/plantuml_encode.py /tmp/diagram.puml |
| Confluence | ```plantuml code block in the Obsidian source file |
Convert to PNG only when publishing |
Diagram Popup plugin (installed): All rendered diagrams (PlantUML, Mermaid, Graphviz) can be opened in a draggable, zoomable popup in Obsidian. This means:
- Complex diagrams are viable in vault notes (user can zoom to read details)
- No need to simplify diagrams for readability at inline scale
- Architecture diagrams, large sequence diagrams, and entity models can include full detail
Rules:
- NEVER generate PNG files for Obsidian vault documents. The plugin renders the code blocks directly.
- ALWAYS keep PlantUML source in the Obsidian file (editable, versionable).
- For GitHub PRs: extract PlantUML blocks to
/tmp/<name>.puml, encode to PNG URL, replace in PR body. Keep source in Obsidian. - Diagrams ALWAYS in English, regardless of the document language.
When to Include Diagrams
| Document type | Required diagrams | Optional |
|---|---|---|
| Feature discovery | Sequence (main flow) | C4 Context |
| Implementation plan | Sequence (main flow), Data Model | Decision Flow, C4 Component |
| Investigation/Bug | Sequence (failure flow) | Before/After state |
| PR Notes | Sequence (what changed) | Data Model (if schema changed) |
| Confluence doc | Architecture Overview, Sequence, Data Model | Decision Flow, Data Flow |
| Runbook | C4 Context, C4 Container | C4 Component |
| Test plan | Sequence (test scenario flow) | Decision Flow |
| ADR | C4 Component (options comparison) | Sequence (proposed flow) |
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.
- 2mo ago First seen · 155 lines · 54 tokens per session scan A 84b333486673
diagrams is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 26d ago), licensed MIT. It adds 54 tokens to every session and 1,535 once invoked, about $0.0002 per session on Opus 5.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
me-card
Render the user's saved /.me/ context as a single ASCII-art infographic card. Use when the user asks to "show my info", "print my card", "render my profile", "me card", "ascii infographic of my dot-me", or invokes the /me-card shortcut. Read-only — never writes to /.me/.
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the chosen backdrop colour, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed…
email-lifecycle-flow-writer
Step of the email-lifecycle playbook: writes one lifecycle flow as a build sheet for the brand's email tool, every message finished in the brand voice. Run email-lifecycle instead; not for direct use.
work-with-creators-creator-vetting
Vets creators you have already named from their public pages. Covers the median views of their last 12 to 20 posts (sponsored and organic apart), a read of their comments, how often they post, audience fit with how sure it is, about 12 months of brand-safety checks, rival partnerships and rules for regulated…
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).