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 robrohan/claude-skills --skill laffaregit clone --depth 1 https://github.com/robrohan/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/robrohan/claude-skills/laffare)<a href="https://agentmods.dev/skills/robrohan/claude-skills/laffare"><img src="https://agentmods.dev/badge/skills/robrohan/claude-skills/laffare/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/robrohan/claude-skills/laffare"><img src="https://agentmods.dev/badge/skills/robrohan/claude-skills/laffare.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.00052 | $0.01188 |
| Opus 5 | $0.00026 | $0.00594 |
| Sonnet 5 | $0.00010 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
laffaire scanned grade A 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(curl:*) How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laffaire
Manage projects and calendar entries in a Laffaire instance via its JSON API.
In Laffaire, a project is called an Event (a named calendar group), and an individual calendar item within it is called an Entry.
Config
Before making any API call, check whether LAFFAIRE_URL and LAFFAIRE_TOKEN are already
set in the environment by running a quick test curl. If a call fails due to missing variables,
ask the user to provide them:
LAFFAIRE_URL— base URL of the Laffaire instance, e.g.https://example.comLAFFAIRE_TOKEN— a Bearer token created from the/-/tokenspage of the UI
Actions
Ask the user what they want to do:
- List projects — list all their events
- Create a project — create a new named event/calendar group
- List entries — list calendar entries in a project
- Add an entry — add a calendar entry to an existing project
- Delete a project or entry
API Reference
All routes are under /api/v1/. All requests must include:
Authorization: Bearer <token>
Content-Type: application/json
Projects (Events)
List all projects
GET /api/v1/events
Returns an array of { id, title, description }.
Create a project
POST /api/v1/events
{ "title": "My Project", "description": "Optional description" }
Returns 201 with { id, title, description }. The id is needed to add entries.
Get a project
GET /api/v1/events/{id}
Update a project
PUT /api/v1/events/{id}
{ "title": "New Title", "description": "New description" }
Delete a project
DELETE /api/v1/events/{id}
Returns 204 No Content.
Entries (Calendar Items)
List entries in a project
GET /api/v1/events/{project_id}/entries
Returns an array of entry objects.
Create an entry
POST /api/v1/entries
{
"event_id": "<project id>",
"subject": "Team standup",
"start_date": "2026-03-10",
"start_time": "09:00",
"end_date": "2026-03-10",
"end_time": "09:30",
"all_day_event": false,
"description": "Daily sync",
"location": "Zoom",
"private": false
}
event_id and subject are required. Returns 201 with the created entry.
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.
- 10d ago First seen · 178 lines · 52 tokens per session scan A 9aff591445bd
laffaire is a skill published in the GitHub repository robrohan/claude-skills (1 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 1,188 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
daily-briefing
Daily orientation and chief-of-staff briefing. Pulls from Slack (saved items), Gmail (important/starred), Google Calendar (today's events), Jira CLI (configured projects), and Todoist CLI, validates every action item, synthesizes a prioritized briefing using three consequence-based tiers, then produces a decisive…
email-to-calendar
Extract calendar events and deadlines from emails and create calendar entries. Two modes: monitor your inbox directly, or process emails you forward to a dedicated address. Trigger when a user asks to scan emails for events, mentions an event in an email, or wants to add something from an email to their calendar.
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
pm
When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban per business (whatever portfolio of businesses, projects, or initiatives you run). Tool-agnostic — connects via API/MCP to whatever PM tool each business uses (Notion, GitHub Projects, Plane, Linear, Obsidian…
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…