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 agentmods add skills/serac-labs/serac/agile-developmentnpx skills add serac-labs/serac --skill agile-developmentgit clone --depth 1 https://github.com/serac-labs/seracWrote 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/serac-labs/serac/agile-development)<a href="https://agentmods.dev/skills/serac-labs/serac/agile-development"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/agile-development.svg" alt="Measured on agentmods" 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 | $0.00068 | $0.02111 |
| Opus 5 | $0.00034 | $0.01056 |
| Sonnet 5 | $0.00014 | $0.00422 |
| Haiku 4.5 | $0.00007 | $0.00211 |
Grade A, and why
agile-development 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 5d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agile Development 2.0
Sixteen tools on rm_* and pm_*. This is the plugin-provided Agile module
(com.snc.sdlc.agile.2.0), not a generic task tracker — the tables are its own and the state values
are numbers behind friendly labels.
Is the plugin even on?
Every table here comes from the plugin. If it is not activated, calls fail with "Invalid table", and the tools say so with the plugin id rather than passing the raw error through. Cheapest check — a read that needs no ids:
await snow_agile_sprint_query({ limit: 1 }) // touches rm_sprint
An instance without the plugin has none of this and no amount of retrying helps.
The model
rm_team a scrum team, with a default velocity
└── rm_team_member one person on it, with a role
rm_sprint a time box, optionally assigned to a team
rm_epic a body of work spanning sprints
└── rm_story the unit of work. Points, state, assignee.
└── rm_scrum_task optional breakdown under a story
rm_release groups sprints and epics for a ship date
Separately, pm_project / pm_project_task is PPM, a different product: waterfall-ish projects with
a manager and dates. snow_create_project and snow_create_project_task write there. Do not mix them
with the rm_* tables — a story is not a project task and nothing joins them.
Order of operations
Team → sprint → story. Every link is a reference lookup that fails if the target is not there yet.
// 1. team
const team = await snow_agile_team_manage({ action: "create", name: "Platform", velocity: 30 })
await snow_agile_team_manage({ action: "add_member", sys_id: team.sys_id,
member: "sam.patel", role: "scrum_master" })
// 2. sprint — the team is resolved by name or sys_id
await snow_agile_sprint_manage({ action: "create", name: "Sprint 24", team: "Platform",
start_date: "2026-09-01", end_date: "2026-09-14", story_points: 30 })
// 3. stories, attached at creation or later
await snow_agile_story_manage({ action: "create", title: "Widen the assignment lookup",
story_points: 5, sprint: "Sprint 24", state: "Ready" })
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.
- 5d ago First seen · 188 lines · 68 tokens per session scan A fcdfcd480ed6
agile-development is a skill published in the GitHub repository serac-labs/serac (78 stars, last pushed 10d ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,111 once invoked, about $0.0003 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-30.
Other skills, from other repositories
contract-review-workflow
Trigger a deployed Mistral Workflow for contract review, poll execution status, detect human-in-the-loop checkpoints via workflowinteract(query), collect approval or changes, and resume the workflow via workflowinteract(signal). Use when the user wants to run a contract through a Mistral Workflow with oversight…
french-commit-message
Génère un message de commit git en français au format Conventional Commits à partir des changements stagés. Récupère automatiquement le diff via git diff --staged. À utiliser quand l'utilisateur demande un commit message, message de commit, ou résumé de diff en français.
cpersona-memory
Give Claude persistent, searchable memory across sessions using the CPersona MCP server. Use this skill whenever the user wants Claude to remember things between conversations, asks to install or set up CPersona / a memory server, or when CPersona tools are available and the conversation contains decisions, rules…
french-invoice-reminder
Rédige une relance de facture B2B en français avec un ton contrôlé (poli, ferme, ou final). À utiliser quand l'utilisateur demande une relance facture, un rappel de paiement, un mail de recouvrement, ou une dunning letter en français.
shippo-support-ticket
Generate a complete, auto-classified, ready-to-paste Shippo support ticket for a single shipment or label. Use when a support agent or customer needs to escalate a shipping issue (lost/delayed package, unused-label refund, billing/rate adjustment, address exception, customs hold, carrier-account, or tracking-webhook…
redazione-contratto
Supporto alla redazione contrattuale con verifica normativa, clausole tipo e compliance GDPR. Usa quando l'utente chiede di redigere, revisionare, analizzare un contratto, verificare clausole o predisporre un accordo.