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 lukedj78/dev-flow --skill scrumgit clone --depth 1 https://github.com/lukedj78/dev-flowWrote 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/lukedj78/dev-flow/scrum)<a href="https://agentmods.dev/skills/lukedj78/dev-flow/scrum"><img src="https://agentmods.dev/badge/skills/lukedj78/dev-flow/scrum/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/lukedj78/dev-flow/scrum"><img src="https://agentmods.dev/badge/skills/lukedj78/dev-flow/scrum.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.00234 | $0.01969 |
| Opus 5.5 | $0.00094 | $0.00788 |
| Sonnet 5.5 | $0.00047 | $0.00394 |
| Haiku 4.5 | $0.00023 | $0.00197 |
Grade A, and why
scrum 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 9d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
scrum — agile scrum on Linear, Jira or GitHub
This skill owns the tracker side of a dev-flow project. It writes to the chosen tracker and to the tracker /
scrum blocks of .workflow/meta.json. It never touches app code, and it never changes phase: it records
state and appends history, and is never a phase gate.
The method is the same on every tracker (references/scrum-model.md); only the adapter changes:
| Reference | How it talks | |
|---|---|---|
| Linear | references/linear.md |
the Linear MCP |
| Jira | references/jira.md |
the Atlassian Rovo MCP; story points with scripts/jira_estimate.py |
| GitHub | references/github.md |
gh; issues with scripts/github_sync.py; a sprint is a milestone |
Issue bodies follow references/issue-standard.md on every tracker. Bugs follow references/triage.md.
The .workflow/ contract is references/contracts.md.
Preconditions
.workflow/meta.jsonexists (a dev-flow project). If not, say so and stop.- The tracker's connection works, checked with a read before any write:
list_teams(Linear),listJiraProjects(Jira),gh auth status(GitHub). No account is created by this skill, and no token goes through the chat: Jira REST readsJIRA_EMAIL/JIRA_API_TOKENfrom the environment, GitHub usesgh auth, the MCPs the user's OAuth. - Setup needs
.workflow/tasks.md(prd-to-tasksfirst). Coupled format:scripts/task_key.pyderives the dedup key from the- [ ] **<Title>** — <body>line, splitting on the em-dash; a hand-edited separator breaks dedup.
Read state, then pick a mode
Run python3 scripts/meta_tracker.py <root>/.workflow/meta.json migrate first when meta.json has an older shape (a
linear block, tracker.kind, a map keyed by title — show_state.py names it): it moves everything into
tracker without dropping a key, and keeps titles it cannot find in tracker.unmatched.
- No
tracker.provider→ Choose. - A provider, no
tracker.project,tasks.mdpresent → Setup. - The project already exists on the tracker but
tracker.projectorissue_mapis missing → Adopt. tracker.projectpresent → Sync.- A bug reported (by the user, a test, an alert) → Triage, whatever the state.
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/contracts.md 85 KB
- references/github.md 2.8 KB
- references/issue-standard.md 2.9 KB
- references/jira.md 6.3 KB
- references/linear.md 4.6 KB
- references/scrum-model.md 2.9 KB
- references/triage.md 2.4 KB
- scripts/github_sync.py 10 KB runs code
- scripts/jira_estimate.py 5.3 KB runs code
- scripts/meta_io.py 9.2 KB runs code
- scripts/meta_tracker.py 9.6 KB runs code
- scripts/task_key.py 1006 B runs code
- scripts/test_github_sync.py 10.0 KB runs code
- scripts/test_jira_estimate.py 6.1 KB runs code
- scripts/test_scripts.py 9.6 KB runs code
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.
- 9d ago First seen · 116 lines · 234 tokens per session scan A b258084074b4
scrum is a skill published in the GitHub repository lukedj78/dev-flow (6 stars, last pushed 5d ago), licensed MIT. It adds 234 tokens to every session and 1,969 once invoked, about $0.0009 per session on Opus 5.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-10-19.
Other skills, from other repositories
sdlc-regulatory
AI-driven SDLC governance framework with quality gates, risk-based autonomy caps, change traceability, Definition of Done, and a compliance crosswalk (EU AI Act, NIST AI RMF, ISO/IEC 42001, SOC 2, GDPR). Use when running or reviewing work through the BMad-style subagent SDLC, enforcing gates, classifying risk, or…
agentrq
Execute tasks assigned by humans or supervisor agents within a specific AgentRQ workspace. Use when you receive channel messages or need to report progress on tasks.
internal-comms
Author clear, high-impact internal engineering communications including 3P status updates, blameless incident postmortems, architecture decision memos, and leadership briefs. Use when writing technical updates, sprint reports, incident reviews, or organizational engineering announcements.
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
swarm-orchestration
Multi-agent swarm formation and coordinated execution with topology-aware agent deployment, consensus protocols, and anti-drift enforcement.
constitution-creation
Establish project governing principles including dev guidelines, code quality standards, testing policies, UX requirements, performance benchmarks, and security constraints.