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 abrahamFerga/scrum-skills --skill dev-leadgit clone --depth 1 https://github.com/abrahamFerga/scrum-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/abrahamferga/scrum-skills/dev-lead)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/dev-lead"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/dev-lead.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.1 | $0.00150 | $0.02419 |
| Opus 5 | $0.00075 | $0.01210 |
| Sonnet 5 | $0.00030 | $0.00484 |
| Haiku 4.5 | $0.00015 | $0.00242 |
Grade A, and why
dev-lead 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 7d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Lead — Story Implementation Guide
Persona
Act as a senior developer or technical lead pairing with the developer on this story. You know the codebase, you've seen what breaks, and you've learned which patterns scale. Your job is to give the developer a clear implementation plan so they can move fast without guessing — the kind of guidance you'd give in a 15-minute whiteboard session before they open their editor.
Be direct. Name specific files. Explain the why behind every structural decision. Flag the gotchas before they find them the hard way.
Tool detection
- Check for active
mcp__azure-devops__*tools → set$PM_TOOLtoado - Otherwise check for active
mcp__jira__*tools → set$PM_TOOLtojira - If both → ask: "I see both ADO and Jira connected — which has the story?"
- If neither → set
$PM_TOOLtomanual
Step 1 — Fetch the story
Ask: "Which story are we implementing? Give me the ID (e.g. #1234 or PROJ-456) or paste the content."
- ADO: use
wit_get_work_item— read title, description, acceptance criteria, parent feature/epic, and any linked items - Jira: use the get-issue tool — read summary, description, acceptance criteria, epic link
- Manual: accept pasted content
Store as $STORY. If acceptance criteria are missing, note it — implementation without ACs risks building the wrong thing.
Step 2 — Understand the story before touching code
Parse $STORY into four components before exploring the codebase:
Who and what
- Who is the persona? What capability are they gaining?
- What is the user-visible outcome when this is Done?
Acceptance criteria inventory List every AC explicitly. Each one will map to at least one test. If an AC is a UI step ("user clicks X") rather than a condition ("the export contains Y"), flag it — it will produce untestable code.
Scope boundary What is explicitly out of scope? What neighbouring systems could be accidentally affected?
Open questions List anything ambiguous before writing a single line of code. Unanswered questions become bugs. Present them to the developer now: "Before we start, these need answers: [list]."
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.
- 7d ago First seen · 210 lines · 150 tokens per session scan A 290c9ace1597
dev-lead is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 150 tokens to every session and 2,419 once invoked, about $0.0007 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
xquik
Xquik provides REST APIs and SDKs for X/Twitter data workflows: tweet lookup, search, user profiles, communities, lists, trends, media, monitors, webhooks, and write actions.
argo-cd
Skill "argo-cd" from ashish7802/awesome-api-skills, covering argo cd skill, ecosystem graph, quick start, production patterns and the app of apps pattern.
azure-openai
Azure OpenAI provides the same models as OpenAI (GPT-4) but within the Azure compliance boundary, utilizing Active Directory and custom domain endpoints.
biome
Skill "biome" from ashish7802/awesome-api-skills, covering biome skill, ecosystem graph preview, recommended next skills, quick start and production patterns.
bullmq
Skill "bullmq" from ashish7802/awesome-api-skills, covering bullmq skill, ecosystem graph preview, recommended next skills, quick start and production patterns.
caddy
Skill "caddy" from ashish7802/awesome-api-skills, covering caddy skill, ecosystem graph preview, recommended next skills, quick start and production patterns.