Borrowing it
Nothing to install: this file belongs to aimasteracc/tree-sitter-analyzer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aimasteracc/tree-sitter-analyzer/main/.claude/skills/tsa-health-watch/SKILL.mdgit clone --depth 1 https://github.com/aimasteracc/tree-sitter-analyzerWrote 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/aimasteracc/tree-sitter-analyzer/tsa-health-watch)<a href="https://agentmods.dev/skills/aimasteracc/tree-sitter-analyzer/tsa-health-watch"><img src="https://agentmods.dev/badge/skills/aimasteracc/tree-sitter-analyzer/tsa-health-watch/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/aimasteracc/tree-sitter-analyzer/tsa-health-watch"><img src="https://agentmods.dev/badge/skills/aimasteracc/tree-sitter-analyzer/tsa-health-watch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00157 | $0.01204 |
| Opus 5 | $0.00078 | $0.00602 |
| Sonnet 5 | $0.00031 | $0.00241 |
| Haiku 4.5 | $0.00016 | $0.00120 |
Grade A, and why
tsa-health-watch 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 11d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tsa-health-watch — Project + file health in one pass
Grades files A→F across 6 dimensions (complexity, structure, dependencies, duplication, size, git-hotspot). Daemon mode alerts on grade drops live.
When to use
| Goal | Tool |
|---|---|
| Project portrait + worst files | health action=project |
| One-file deep dive | health action=file |
| Top hubs + sensory neurons | health action=overview |
| Find dead functions | health action=dead |
| Complexity hotspots (visualize) | health action=heatmap |
| Watch & alert on degradation | --watch-health CLI (Bash) |
Procedure
One-shot triage (cold-start health audit)
Fan out in one message:
health action=projectwithmax_files: 20— grade distribution + worst-20health action=deadwithmax_dead: 50— pruning candidateshealth action=overview— hub functions + entry points + 0-degree leaves
Read the verdict. If D/F files exist in worst-20, drill into each with
health action=file to get the per-dimension breakdown + recommendation.
Single-file investigation
health action=file file_path="<path>"
Returns:
grade: A | B | C | D | F (overall)dimensions: {complexity, structure, dependencies, duplication, size, git_hotspot}weakest_dimension: which one dragged grade downsignal: healthy | moderate_depth | high_complexity | etc.recommendation: next concrete action
Long-running watch (daemon mode, T4)
Run in a separate terminal:
uv run tree-sitter-analyzer --watch-health \
--threshold-grade C \
--watch-interval 60 \
--notify-channel stdout,file \
--notify-file .tree-sitter-cache/health-events.jsonl \
--on-degradation 'echo "ALERT: {file} {previous_grade}→{grade} ({recommendation})"'
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.
- 11d ago First seen · 136 lines · 157 tokens per session scan A 25777d2ccc3a
tsa-health-watch is a skill published in the GitHub repository aimasteracc/tree-sitter-analyzer (49 stars, last pushed today), licensed MIT. It adds 157 tokens to every session and 1,204 once invoked, about $0.0008 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-30.
Other skills, from other repositories
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by OpenBitFun's unified Review mechanism instead.…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
pr-review-canvas
Create a OpenBitFun Canvas for reviewing a pull request, branch diff, or change set with Cursor-style diff cards, review maps, risk callouts, and focused reviewer flow. Use when the user asks for a PR review canvas, diff walkthrough, change-set overview, or visual review summary.
memstack-development-code-reviewer
Use this skill when the user says 'review code', 'code review', 'check my code', 'audit this', 'review PR', 'review changes', 'what's wrong with this', or is requesting a structured review of code quality, security, performance, or maintainability. Do NOT use for refactoring plans or test generation.
shard
Use when the user says 'shard this', 'split file', or when working with files over 1000 lines.