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.
/plugin marketplace add shashankreddy509/claude-tdd-kitnpx agentmods add plugins/shashankreddy509/claude-tdd-kit/dev-daygit 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.svg" alt="Measured on agentmods" 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 3d 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": "dev-day",
"version": "1.5.4",
"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. 10 skills travel with it, and installing the plugin installs all of them — 1,024 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill start-session A 67 tokens
- Skill bug-triage A 163 tokens
- Skill condense-feedback A 99 tokens
- Skill create-ticket A 112 tokens
- Skill standup A 105 tokens
- Skill jira-comment A 104 tokens
- Skill merge-feedback A 74 tokens
- Skill groom A 134 tokens
- Skill prove-pre-existing A 105 tokens
- Skill end-session C 61 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.
- 3d ago First seen · 19 lines scan A 3015bac52d32
dev-day is a plugin published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 10d ago), 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
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.
allbeads
Multi-repo orchestration for AI agent workflows. Aggregate beads across repositories, manage contexts, and coordinate distributed work.
jira
Jira integration for issue tracking, project management, and workflow automation. Create, update, and search issues directly from Claude.
workingon
Claude Code skill and hooks that record your work in Jira, Linear, GitHub Issues, Trello or Vikunja.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
jira-mcp-ai
Jira Cloud tools for Claude Code: JQL search, issue reads, and writes behind a plan/apply gate.