Borrowing it
Nothing to install: this file belongs to Federico-Anastasi/DYLA-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Federico-Anastasi/DYLA-ai/main/.agents/skills/diagram/SKILL.mdgit clone --depth 1 https://github.com/Federico-Anastasi/DYLA-aiWrote 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/federico-anastasi/dyla-ai/diagram)<a href="https://agentmods.dev/skills/federico-anastasi/dyla-ai/diagram"><img src="https://agentmods.dev/badge/skills/federico-anastasi/dyla-ai/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/federico-anastasi/dyla-ai/diagram"><img src="https://agentmods.dev/badge/skills/federico-anastasi/dyla-ai/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.00042 | $0.02212 |
| Opus 5 | $0.00021 | $0.01106 |
| Sonnet 5 | $0.00008 | $0.00442 |
| Haiku 4.5 | $0.00004 | $0.00221 |
Grade A, and why
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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/diagram — Technical diagrams
Reads the project material and produces the technical diagrams: architecture views (systems and integrations, SAI-style), operational workflows, dataflows (who touches which data — also the base for data-privacy mapping), sequence diagrams for the exchanges that need step-by-step precision.
UX: chat stays conversational. The deliverable is never drawn in chat — the user
sees and edits the diagrams on the canvas in the viewer, from diagram.json. In chat
you discuss in words, citing diagrams and nodes by id (e.g. the crm node in
arch-overview). When you cite a chapter of the brief, write [[brief:Chapter title]].
PROTOCOL
- Read context.md — where is the project? (Diagrams already discussed? Decisions taken?)
- Read the material — brief, data model, estimate, meetings (see PHASE 1)
- If
diagram.jsonalready exists: ask "Edit it, or regenerate from scratch?" - Q&A (BLOCKING — 3 to 5 questions, no more): which diagrams, which scope
- Write diagram.json straight away with
meta.status: "draft" - Present a conversational summary (BLOCKING — wait for validation or edits)
- On confirmation: set
meta.status: "confirmed" - Update context.md
Note: diagram.html is an export, generated on demand by the backend from
diagram.json (GET /api/projects/{project}/export/diagram.html) — a single
self-contained file the client opens with a double click. This skill does not produce it.
PHASE 1 — READING
Read ALL of these before you go on:
- the brief:
projects/{project}/brief.json, or the input document (brief.md, or its extracted text under.extracted/) projects/{project}/data_model.json— if it exists: the entities and integrations it names are the backbone of the architecture and dataflow viewsprojects/{project}/estimate.json— if it exists: the epics tell you which systems and flows the project actually touchesprojects/{project}/meetings/*anddocs/*— processes are usually described thereprojects/{project}/context.mdprojects/{project}/diagram.json— if it exists
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 · 186 lines · 42 tokens per session scan A f42fb3aa598a
diagram is a skill published in the GitHub repository Federico-Anastasi/DYLA-ai (2 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 2,212 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-31.
Other skills, from other repositories
contribute-spec-fix
Fix a broken OpenAPI spec in jentic-public-apis with an OpenAPI Overlay, validate it (spectral lint + idempotency check), and contribute it back via a PR to the community catalog. Falls back to applying the same overlay to the local Jentic registry if the user can't wait for maintainer approval, and closes the loop by…
returns-policy
Answer return, refund, and warranty questions for electronics. Use when the user mentions returns, refunds, RMAs, warranty coverage, damaged items, or opened packaging.
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
jentic
Use this skill whenever the user wants to work with a third-party or external API/tool through the Jentic platform — e.g. asks to "find the vessel-tracking API and add it", "get rows from this Google Sheet", connect Slack, import/search/discover an API, integrate or automate a SaaS, pull data from a service, or call…
fabrik-review
Use when operating as the Fabrik Review stage agent. This skill guides code review of an implementation, finding and fixing issues, and ensuring the PR is ready for human review.
fabrik-implement
Use when operating as the Fabrik Implement stage agent. This skill guides the implementation of a planned feature, following the task checklist to produce committed, tested, pushed code on a feature branch.