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 CodeInfinity1/Stram --skill architecture-diagramsgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/architecture-diagrams)<a href="https://agentmods.dev/skills/codeinfinity1/stram/architecture-diagrams"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/architecture-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/codeinfinity1/stram/architecture-diagrams"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/architecture-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.00031 | $0.00482 |
| Opus 5.5 | $0.00012 | $0.00193 |
| Sonnet 5.5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
architecture-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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Diagrams
Purpose
Make complex systems understandable through accurate diagrams. Diagrams must reflect inspected architecture, not imagined components.
When To Use
Use for agent architecture, API flows, deployment maps, data pipelines, sequence diagrams, and module relationships.
Inputs And Evidence
- Source files, docs, services, endpoints, data flows, and user target audience.
- Desired diagram format.
Tool Map
codebase-inspectionread_filesearch_workspacediagram_artifact_creatediagram_artifact_inspectexcalidraw_diagram_createcanvas_a2ui_createcanvas_a2ui_renderwrite_note
Workflow
- Inspect the actual system path.
- Choose diagram type: component, sequence, data-flow, deployment, or state.
- Include only evidenced components or clearly mark proposed ones.
- Use
diagram_artifact_createfor local Markdown, JSON, and Mermaid sidecars with typed nodes, edges, evidence refs, and status. - Use
diagram_artifact_inspectbefore reporting the diagram. - Use
excalidraw_diagram_createonly when a hand-drawn compatible file is requested. - Render/verify artifacts when using canvas.
- Add a short explanation of key flows and unknowns.
Native Implementation Boundaries
- Use Stram markdown/canvas/file tools.
- Do not import external reference architecture-diagram scripts.
- Do not make diagrams from stale assumptions.
- Native diagram artifacts must mark
current,proposed, ordraftstatus explicitly.
Safety And Approval
- Architecture may reveal security details; keep sensitive diagrams local unless approved.
- Avoid exposing secrets or internal URLs unnecessarily.
Verification
- Map diagram nodes to files/docs.
- Verify rendered artifact if generated.
- Inspect diagram artifacts for node count, edge count, evidence refs, and unknowns.
- Mark proposed/future architecture.
Failure Modes
- Flat diagrams with no data flow.
- Mixing current and desired state.
- Missing ownership boundaries.
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.
- 1mo ago First seen · 72 lines · 31 tokens per session scan A 79dd7b42c4b1
architecture-diagrams is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 482 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
product-research
Find and compare current FF&E candidates from a design brief, with sourced purchasing facts and optional CSV-library save. Use to research or source products; not to match from an image or pair coordinating items.
design-craft
Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique. Use for new screens, landing pages, redesigns, typography/layout work, or UI that feels generic or AI-generated. For small fixes, preserve the existing design without starting a…
platform-conventions
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).
antv-x6-editor
A skill for creating and troubleshooting interactive diagrams with AntV X6, a JavaScript engine for editors made of connected nodes and lines. It supports diagram types such as flowcharts, dependency graphs, entity-relationship diagrams, and organization charts.
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
antv-infographic
Create beautiful infographics based on given text content. Use when users request to create infographics.