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/deck/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/deck)<a href="https://agentmods.dev/skills/federico-anastasi/dyla-ai/deck"><img src="https://agentmods.dev/badge/skills/federico-anastasi/dyla-ai/deck/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/deck"><img src="https://agentmods.dev/badge/skills/federico-anastasi/dyla-ai/deck.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.00046 | $0.02557 |
| Opus 5 | $0.00023 | $0.01278 |
| Sonnet 5 | $0.00009 | $0.00511 |
| Haiku 4.5 | $0.00005 | $0.00256 |
Grade A, and why
deck 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deck — Project decks
A status report is not a document you write once: you redo it every week or two for the whole life of the project. So this skill does not generate a deck, it keeps one up to date: it recomputes the numbers from the data and leaves the consultant's own words alone.
Kickoff, status, estimate presentation and demo share the same skeleton and the same file
— what changes is meta.type.
UX: chat stays conversational. Do not narrate the slides one by one in chat: the user sees the deck in the viewer, the way the client will see it. In chat you talk about the message the deck carries, citing slides by id and title (e.g. "S4, the progress slide").
PROTOCOL
- Ask what kind of deck if the request does not make it obvious (a
questionsblock — format in.Codex/prompts/questions_format.md) - Read the estimate, timeline, brief, people and context.md
- If the deck exists: update it, preserving the hand-written slides
- Write deck.json straight away with
meta.status: "draft" - Say in words what the deck says (BLOCKING)
- On confirmation:
meta.status: "confirmed" - Update context.md
PHASE 1 — TYPE OF DECK
| type | When | What it has to get across |
|---|---|---|
kickoff |
At the start | What we will do, who does it, by when, how we work together |
status |
Every 1-2 weeks | Where we are, what changed, what worries us |
estimate |
At the approval meeting | What it costs and why, on which assumptions |
demo |
At demos with users | What can be seen today, and in what order to show it |
If the project already has a deck.json of a different type, ask in a ```questions
block (format in .Codex/prompts/questions_format.md): a project holds one deck at a
time in this file, and replacing it is the user's decision, not yours.
```questions
[
{
"id": 1,
"q": "This project already has a '{existing_type}' deck.json. A project holds one deck at a time in this file — replace it with a '{new_type}' deck, or keep working on the existing one?",
"options": ["Replace it with the new deck", "Keep the existing deck"]
}
]
```
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 · 215 lines · 46 tokens per session scan A efcdadc33b3d
deck is a skill published in the GitHub repository Federico-Anastasi/DYLA-ai (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 2,557 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
onboard
Interviews someone about a software project as a whole — the problem it solves, who it serves, what is in and out of scope, the hard constraints, and the domain vocabulary — and writes it up as a project constitution that every later feature specification inherits. Use this at the start of a project, before any…
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.
fabrik-plan
Use when operating as the Fabrik Plan stage agent. This skill guides the design of an implementation approach, producing a concrete plan with task checklist that the Implement stage will follow.
fabrik-setup
Bootstrap a project to use Fabrik (the GitHub-Project-driven SDLC pipeline orchestrator that drives Claude Code workers through Specify/Research/Plan/Implement/Review/Validate stages). Use this skill when the user wants to install, set up, initialize, or get started with Fabrik for the first time — especially when…
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…
trailhead-view
Skill "trailhead-view" from ToRvaLDz/trailhead, covering load first, in order, routing: verb to engine, render the map: map [map], 🎯 destination and 🗒️ notes.