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 sethdford/claude-skills --skill context-diagramgit clone --depth 1 https://github.com/sethdford/claude-skillsWrote 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/sethdford/claude-skills/context-diagram)<a href="https://agentmods.dev/skills/sethdford/claude-skills/context-diagram"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/context-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/sethdford/claude-skills/context-diagram"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/context-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.00030 | $0.00582 |
| Opus 5 | $0.00015 | $0.00291 |
| Sonnet 5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
context-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 11d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Diagram
Create clear, high-level diagrams showing system boundaries and external interactions.
Context
You are creating context diagrams to establish system scope. Show what's inside vs outside. Identify external dependencies and user interactions. Read system requirements and interfaces.
Domain Context
Based on C4 model and systems thinking:
- System Boundary: What's included? Often misaligned between teams. Clear boundary prevents scope creep.
- External Systems: Payment processors, email services, third-party APIs. Owned by others; you depend on them.
- Users/Actors: Who uses the system? Customers, admins, automated systems. Different users have different interaction patterns.
- Data Flows: What data crosses the boundary? In what direction? Frequency? Synchronous or asynchronous?
Instructions
-
Draw Central Rectangle: This is "your system" (e.g., "E-commerce Platform").
-
Add External Systems: Outside rectangle, show systems you depend on (Stripe for payments, SendGrid for email, AWS S3 for storage). Label communication protocol (REST, webhook, batch).
-
Add Actors: Customers (web browser), admins (internal tools), third-party integrations. Arrows show interaction direction and protocol.
-
Label Data Flows:
- "Customer → Platform: Order request (REST, JSON)"
- "Platform → Stripe: Payment (REST, HTTPS)"
- "Platform → Email Service: Confirmation (REST, webhook)"
-
Keep Simple: One diagram, not multi-level. Aim for ~5-10 external entities. More = split into smaller diagrams or go to container level.
Anti-Patterns
- Too Detailed: Show internal components in context diagram. Result: defeats purpose of high-level view. Guard: Only show external systems and major actors.
- Unclear Boundaries: "Is authentication part of the system?" Result: confusion. Guard: Explicitly define what's in/out. If shared, explain ownership.
- No Data Flow Labels: Assume readers know what data flows. Result: ambiguity. Guard: Label every arrow: "Customer data (GDPR-sensitive)", "Metrics (non-sensitive)".
- Outdated Diagram: New external integration added, diagram not updated. Result: wrong mental model. Guard: Update when external dependencies change; periodic review.
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.
- 11d ago First seen · 50 lines · 30 tokens per session scan A a5733eb41834
context-diagram is a skill published in the GitHub repository sethdford/claude-skills (40 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 582 once invoked, about $0.0002 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 skills, from other repositories
videodb
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize…
lead-intelligence
AI-native lead intelligence and outreach pipeline. Replaces Apollo, Clay, and ZoomInfo with agent-powered signal scoring, mutual ranking, warm path discovery, and personalized outreach. Use when the user wants to find, qualify, and reach high-value contacts.
springboot-verification
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
team-builder
Interactive agent picker for composing and dispatching parallel teams.
cmd_aside
Answer a quick side question without interrupting or losing context from the current task. Resume work automatically after answering.
seo
Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.