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 agentmods add skills/joshidikshant/devsquad/git-healthnpx skills add joshidikshant/devsquad --skill git-healthgit clone --depth 1 https://github.com/joshidikshant/devsquadWhat 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 | $0.00034 | $0.00643 |
| Opus 5 | $0.00017 | $0.00321 |
| Sonnet 5 | $0.00007 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
git-health 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 2d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Health Skill
Scans the repository for common issues that impede workflow and reports actionable remediation steps.
Checks Performed
- Broken Symlinks (GHLT-01): Finds symlinks whose targets do not exist
- Orphaned Branches (GHLT-02): Detects branches with no new commits in N days (default: 30)
- Uncommitted Changes (GHLT-03): Identifies changes not yet pushed to remote, categorized by severity
When to Use
Invoke before starting major work, after a long absence from a project, or when experiencing unexplained tool failures (often caused by broken symlinks).
Usage
bash "${CLAUDE_PLUGIN_ROOT}/skills/git-health/scripts/git-health.sh"
For machine-readable output:
bash "${CLAUDE_PLUGIN_ROOT}/skills/git-health/scripts/git-health.sh" --json
To run only a specific check:
bash "${CLAUDE_PLUGIN_ROOT}/skills/git-health/scripts/git-health.sh" --check symlinks
bash "${CLAUDE_PLUGIN_ROOT}/skills/git-health/scripts/git-health.sh" --check branches
bash "${CLAUDE_PLUGIN_ROOT}/skills/git-health/scripts/git-health.sh" --check changes
Output Format
Human-Readable (default)
=== Git Health Check ===
Broken Symlinks: 2 issue(s) found
.git/hooks/pre-commit -> ../missing-hook [DELETE: git rm .git/hooks/pre-commit]
node_modules/.bin/tsc -> ../typescript/bin/tsc [REINSTALL: npm install]
Orphaned Branches: 1 issue(s) found
feature/old-experiment (last commit: 45 days ago) [DELETE: git branch -d feature/old-experiment]
Uncommitted Changes: 3 issue(s) found
[STAGED] src/auth.ts
[MODIFIED] src/config.ts
[UNTRACKED] .env.local [WARNING: may contain secrets]
Summary: 6 issue(s) across 3 check(s). Run with --fix to apply suggestions.
JSON Format (with --json)
{
"timestamp": "2026-02-18T10:00:00Z",
"checks": {
"symlinks": { "count": 2, "issues": [...] },
"branches": { "count": 1, "issues": [...] },
"changes": { "count": 3, "issues": [...] }
},
"total_issues": 6
}
What ships with it
4 files 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.
- 2d ago First seen · 78 lines · 34 tokens per session scan A ce34054352f8
git-health is a skill published in the GitHub repository joshidikshant/devsquad (7 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 643 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.