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 shashankreddy509/claude-tdd-kit --skill standupgit 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/skills/shashankreddy509/claude-tdd-kit/standup)<a href="https://agentmods.dev/skills/shashankreddy509/claude-tdd-kit/standup"><img src="https://agentmods.dev/badge/skills/shashankreddy509/claude-tdd-kit/standup/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/shashankreddy509/claude-tdd-kit/standup"><img src="https://agentmods.dev/badge/skills/shashankreddy509/claude-tdd-kit/standup.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.00105 | $0.02307 |
| Opus 5 | $0.00053 | $0.01154 |
| Sonnet 5 | $0.00021 | $0.00461 |
| Haiku 4.5 | $0.00011 | $0.00231 |
Grade A, and why
standup 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 9d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
standup
One read-only sweep that answers "anything pending?" from LIVE state, never from memory or a todo file. Sweeps four sources and prints a tight status. Acts on nothing — no commit, push, merge, tag, or transition. If the sweep finds work, it lists it and stops; the user decides what to do next.
The four sources
Run the deterministic sweep (sources 1–3) via the script, then add the Jira source, then print the combined standup.
Sources 1–3 — git + gh + deploy gap — are emitted as RAW facts by one bundled script. Run it and read its output; do NOT re-derive these by hand.
Resolve SKILL_DIR first. Set it to the absolute path of the directory containing THIS
SKILL.md you just Read — your harness reported that path in the Read result. The script is always
a direct sibling of this file (SKILL_DIR/scripts/standup.sh), in every install layout:
Read ~/.claude/plugins/cache/<marketplace>/dev-day/<ver>/skills/standup/SKILL.md → SKILL_DIR=…/skills/standup
Read ~/.claude/skills/standup/SKILL.md → SKILL_DIR=~/.claude/skills/standup
Substitute that literal path below. This works on every harness without relying on a harness-specific environment variable.
"${SKILL_DIR}/scripts/standup.sh" # optionally: --app-paths "app/ src/" (or STANDUP_APP_PATHS=)
Run it from the repo you are reporting on — it reads the CURRENT working directory's git state, not
SKILL_DIR's.
Fallback if that script cannot be run (not found under SKILL_DIR, or not executable). Do NOT
abort; derive sources 1–3 by hand, read-only:
- git:
git rev-parse --abbrev-ref HEAD,git status --short,git rev-list --left-right --count @{u}...HEAD. - PRs:
gh pr list --state open --json number,title,headRefName— targeting the RESOLVED repo (-R <owner/repo>), not necessarily the cwd (see the dashboard section below). - deploy gap: latest plain
v*tag (exclude-rc) vsorigin/main;git diff --name-only <tag>..origin/mainfiltered to the repo's app-source prefix (see--app-pathsbelow). Zero app files → up-to-date; else pending vX.Y.(Z+1).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 148 lines · 105 tokens per session scan A a68fe3b9b3da
standup is a skill published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 17d ago), licensed MIT. It adds 105 tokens to every session and 2,307 once invoked, about $0.0005 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
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
implement-issue
Drive a GitHub issue from branch to pull request — read the issue, create a feature branch, implement the change, run the project's build and tests, then commit, push, and open a PR. Language and build-tool agnostic. Use when asked to implement, fix, or resolve a GitHub issue by number.
jira-time-tracking
Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations…
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
jira-custom-fields
Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA…
jira-issue-management
Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile)…