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 flonat/flonat-research --skill project-deckgit clone --depth 1 https://github.com/flonat/flonat-researchWrote 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/flonat/flonat-research/project-deck)<a href="https://agentmods.dev/skills/flonat/flonat-research/project-deck"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/project-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/flonat/flonat-research/project-deck"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/project-deck.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 76 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
- high Anti-Refusal · line 83 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00056 | $0.00788 |
| Opus 5 | $0.00028 | $0.00394 |
| Sonnet 5 | $0.00011 | $0.00158 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade B, and why
project-deck scanned grade B with 1 finding 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 8d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Compile without warnings (fix overfull hboxes) How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Deck Skill
Create beautiful presentation decks to communicate project status to your future self and collaborators.
Purpose
Based on Scott Cunningham's Part 7: "Making Beautiful Decks For My Future Self" - using decks not for public speaking but to efficiently communicate work status across time and to coauthors.
The Philosophy
"I use decks to help me keep track of the work I was doing so that I can communicate it to my coauthors and myself later in the week when we meet to go over our projects."
Claude has absorbed the "rhetoric of decks" - the tacit knowledge about what makes presentations effective:
- One idea per slide
- Titles are assertions, not labels
- Lead with conclusions
- Visual hierarchy signals importance
- Repeat for retention
- Transition explicitly
When to Use
- Before a supervisor meeting
- At the end of a research sprint
- When handing off to a coauthor
- When returning to a dormant project
- Weekly project status updates
Workflow
- Read project context - Progress logs, current focus, recent work
- Design deck structure:
- Research question
- What's been done (with figures/tables)
- Key findings so far
- Current blockers
- Next steps
- Create beautiful output - Clean design, good typography, optimal cognitive density
- Include visuals - Figures, tables, diagrams that capture the work
Deck Rhetoric Principles
## Principles for Effective Decks
1. **One idea per slide** - Don't overload
2. **Titles are assertions** - "Distance increases abortion rates" not "Results"
3. **Lead with conclusions** - Don't bury the lede
4. **Visual hierarchy** - Most important things stand out
5. **Optimal cognitive density** - Smooth delivery, not overloaded
6. **Beautiful figures and tables** - Data visualisation matters
7. **Explicit transitions** - Guide the reader through the narrative
Extended Rhetoric Principles
For Research Decks
- Motivation slides: Why should anyone care? What's the gap?
- Methods slides: Identification strategy in plain English, visualize variation
- Results slides: Lead with main coefficient, visualize where possible
- Figures: Clear titles, labeled axes, no chartjunk
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.
- 8d ago First seen · 88 lines · 56 tokens per session scan B 401416fd97bd
project-deck is a skill published in the GitHub repository flonat/flonat-research (133 stars, last pushed 16d ago), licensed MIT. It adds 56 tokens to every session and 788 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
buffer-sizing
Calculate project, feeding, and resource buffers — shared with implementation-planning.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
shared-monorepo-turborepo
Turborepo, workspaces, package architecture, @repo/ naming, exports, tree-shaking.
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
speckit-companion-specify
../../../.specify/extensions/companion/.specify-dev/agent-commands/claude/speckit-companion-specify/SKILL.md.