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 daily-sync-devgit 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/daily-sync-dev)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/daily-sync-dev"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/daily-sync-dev.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.00116 | $0.01237 |
| Opus 5 | $0.00058 | $0.00619 |
| Sonnet 5 | $0.00023 | $0.00247 |
| Haiku 4.5 | $0.00012 | $0.00124 |
Grade A, and why
daily-sync-dev 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Scrum — Developer Update
Scrum Guide grounding
The Daily Scrum is a 15-minute event for Developers. Its purpose is to inspect progress toward the Sprint Goal and produce an actionable plan for the next day.
Key rules this skill enforces:
- It is not a status report to management or the Scrum Master.
- The 2020 Scrum Guide removed the mandatory three questions — any structure that serves the team is valid.
- Focus is on the Sprint Goal, not individual task counts.
Tool detection
Identify which project management tool is available before proceeding:
- Check for active
mcp__azure-devops__*tools → set$PM_TOOLtoado - Otherwise check for active
mcp__jira__*tools → set$PM_TOOLtojira - If both are available → ask: "I see both ADO and Jira connected — which should I use?"
- If neither is available → set
$PM_TOOLtomanual
Step 1 — Identify the developer
Ask: "What's your name or username as it appears in your PM tool?"
Store as $DEVELOPER. If skipped, proceed with whatever items are returned and note that attribution may be incomplete.
Step 2 — Fetch the Sprint Goal
Retrieve the Sprint Goal from the current sprint or iteration.
- ADO: Query the current iteration node for its goal field.
- Jira: Query the active sprint's
goalfield. - Manual: Ask the developer directly.
Store as $SPRINT_GOAL. If unavailable, proceed and note that a missing Sprint Goal is a team health issue worth raising.
Step 3 — Fetch Sprint Backlog items
Use the available MCP tools to retrieve work items assigned to $DEVELOPER in the current sprint:
- ADO: use
wit_my_work_itemsorwit_get_work_items_for_iterationfor the current iteration - Jira: use the equivalent sprint issue listing tool
- Manual: ask the developer to paste their items directly into the chat
Group the results into:
| Bucket | Criteria |
|---|---|
| Done since last sync | State moved to Done / Resolved / Closed in the last 24 h |
| In Progress | Active / In Progress state |
| Planned | To Do / New — sprint-committed but not started |
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 · 140 lines · 116 tokens per session scan A 74690a8268e5
daily-sync-dev is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 116 tokens to every session and 1,237 once invoked, about $0.0006 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
turborepo
Skill "turborepo" from ashish7802/awesome-api-skills, covering turborepo skill, ecosystem graph preview, recommended next skills, quick start and production patterns.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
devflow-planning
AI-powered sprint planning, velocity analysis, and capacity forecasting. Use for planning sprints, predicting outcomes, and providing agile recommendations based on historical data.
git-jira-integration
Integration between Git workflows and Jira issues. Generates branch names from issues, validates commit messages, and provides PR context from Jira specifications.
jira-read
Read data from Jira including issues, comments, sprints, and execute JQL queries. Use when you need to fetch or search Jira data without making changes.