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/shashankreddy509/claude-tdd-kitWrote 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/shashankreddy509/claude-tdd-kit/dev-day)<a href="https://agentmods.dev/plugins/shashankreddy509/claude-tdd-kit/dev-day"><img src="https://agentmods.dev/badge/plugins/shashankreddy509/claude-tdd-kit/dev-day/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/shashankreddy509/claude-tdd-kit/dev-day"><img src="https://agentmods.dev/badge/plugins/shashankreddy509/claude-tdd-kit/dev-day.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dev-day 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 today.
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": "dev-day",
"version": "1.17.5",
"description": "The complete developer day-loop for Claude Code + Jira: /start-session boots a senior-collaborator session (feedback memory, Jira backlog, standing plan-gate), /standup answers 'anything pending?', /bug-triage root-causes tickets, /groom preps them for estimation, /create-ticket files them, /jira-comment posts clean Jira comments, and /end-session captures what the session learned into feedback.md for the next one. Building a ticket is handed off to the tdd-pipeline plugin (/tdd-pipeline:build then /tdd-pipeline:implement).",
"author": {
"name": "Shashank Reddy Ganta"
},
"keywords": [
"workflow",
"jira",
"session",
"standup",
"triage",
"grooming",
"feedback",
"dev-loop"
]
}
What it installs
The manifest is a name and a version. 12 skills travel with it, and installing the plugin installs all of them — 846 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill groom-panel A 241 tokens
- Skill start-session A 0 tokens
- Skill bug-triage A 0 tokens
- Skill condense-feedback A 99 tokens
- Skill end-session A 0 tokens
- Skill shape-idea A 154 tokens
- Skill create-ticket A 112 tokens
- Skill merge-feedback A 0 tokens
- Skill standup A 106 tokens
- Skill jira-comment A 0 tokens
- Skill groom A 134 tokens
- Skill prove-pre-existing A 0 tokens
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.
- today Changed 3be00474c7a3
- 4d ago Changed d198d351a180
- 5d ago Changed 17ce997a683c
- 6d ago Changed a7f32c0288ca
- 7d ago Changed bd5f8a207580
- 11d ago Changed 16527ecbb7ad
- 12d ago Changed 524ee355d439
- 16d ago Changed a68d6bfcb327
- 20d ago Changed 88bc6086b4c9
- 23d ago First seen · 19 lines scan A 0ba82e61d7c6
dev-day is a plugin published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed today), licensed MIT. 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
jira-assistant-skills
One Jira skill: the Entry-Point Hint for the jira-as CLI 2.x. Run jira-as help first.
fullstack-dev-kit
Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.
unfurl-context
Unfurls Jira tickets, GitHub PRs/issues/repos/files, GitLab issues/MRs/projects/files, and Sentry issues referenced in your prompt into context Claude can read.
fullstack-dev-kit
Issue-to-PR workflow for any tech stack: fetch stories from Jira/Linear/GitHub/Azure and Figma designs, plan-approval gate, adaptive quality + coverage gates, e2e generation, PR creation and review.
jira
Jira integration for issue tracking, project management, and workflow automation. Create, update, and search issues directly from Claude.
mcp-atlassian-extended
Jira/Confluence MCP server (MCP 2026-07-28): sprints, boards, attachments; writes or read-only.