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.
git clone --depth 1 https://github.com/ebursztein/sprintyWrote 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/plugins/ebursztein/sprinty/claude)<a href="https://agentmods.dev/plugins/ebursztein/sprinty/claude"><img src="https://agentmods.dev/badge/plugins/ebursztein/sprinty/claude/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/plugins/ebursztein/sprinty/claude"><img src="https://agentmods.dev/badge/plugins/ebursztein/sprinty/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sprinty 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 16d 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.
What it actually says
{
"name": "sprinty",
"version": "0.2.2",
"description": "Disciplined sprint workflow with dashboard-at-start, feature subsprints, artifacts, an immutable git-anchored ledger, and programmatic close gates.",
"author": { "name": "Elie Bursztein" },
"homepage": "https://github.com/ebursztein/sprinty",
"repository": "https://github.com/ebursztein/sprinty",
"license": "Apache-2.0",
"keywords": ["sprint", "discipline", "ledger", "mcp", "dashboard"]
}
What it installs
The manifest is a name and a version. 2 skills, 1 hook, 1 MCP server travel with it, and installing the plugin installs all of them — 186 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 16d ago Changed 27016ff19c6b
- 1mo ago Changed 9436dc86b785
- 2mo ago First seen · 11 lines scan A 6c67c61d2d01
sprinty is a plugin published in the GitHub repository ebursztein/sprinty (0 stars, last pushed 16d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
dev-workflow
Plan features with structured PRDs, checkpoint progress, and resume across sessions.
make-it-real
Guided discovery skill for turning vague ideas into project specs, delivery scopes, and AI-agent handoffs.
ravenclaw
Personal work context management for AI-powered development. Track epics, issues, wiki pages, and knowledge ontology across AI agent sessions.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.