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 sm-impediment-loggit 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/sm-impediment-log)<a href="https://agentmods.dev/skills/abrahamferga/scrum-skills/sm-impediment-log"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/sm-impediment-log/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/abrahamferga/scrum-skills/sm-impediment-log"><img src="https://agentmods.dev/badge/skills/abrahamferga/scrum-skills/sm-impediment-log.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.00122 | $0.01539 |
| Opus 5 | $0.00061 | $0.00770 |
| Sonnet 5 | $0.00024 | $0.00308 |
| Haiku 4.5 | $0.00012 | $0.00154 |
Grade A, and why
sm-impediment-log 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 11d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Impediment Log
Purpose
An impediment is anything outside the team's control that slows or blocks Sprint progress. The Scrum Master's job is to make them visible, get them assigned, and get them resolved — fast. An unlogged impediment is invisible to stakeholders. An impediment with no owner and no target date is a blocker in waiting. This skill makes logging fast and tracking honest.
Tool detection
- Check for active
mcp__azure-devops__*tools →$PM_TOOL = ado - If neither ADO nor Jira →
$PM_TOOL = manual
Mode detection
The user is either:
- Logging a new impediment — phrases like "log this", "we have a blocker", "add an impediment"
- Reviewing open impediments — phrases like "what's open", "show impediments", "any overdue blockers"
- Resolving/updating an impediment — phrases like "that's resolved", "update the blocker", "close this impediment"
Handle each mode below.
Mode A — Log a new impediment
Collect the details
Gather (or ask for) the following:
| Field | Description | Required |
|---|---|---|
| Title | One-line summary — what is blocked | Yes |
| Blocker description | What is the impediment, where it came from, why it exists | Yes |
| Affected story/team member | Which Sprint item or person is blocked | Yes |
| Impact | What happens if this is not resolved — does the Sprint goal slip? | Yes |
| Owner | Who is responsible for resolving it (often the SM, sometimes PO or external) | Yes |
| Target resolution date | When must this be resolved to avoid Sprint impact | Yes |
| Escalation required | Does this need to go above the team (management, external vendor, another team)? | Yes |
Create the work item
ADO: use wit_create_work_item with type Impediment (if the process template supports it) or Issue. Set:
- Title:
[BLOCKER] [title] - Description: blocker description + impact
- Tags:
impediment, plusescalation-neededif escalation is required - Priority: 1 if Sprint goal is at risk, 2 otherwise
- Assigned To: owner
- Target Date (custom field or iteration target)
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.
- 11d ago First seen · 150 lines · 122 tokens per session scan A 2651fe3a6288
sm-impediment-log is a skill published in the GitHub repository abrahamFerga/scrum-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 122 tokens to every session and 1,539 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.
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.