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-temporal/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-temporal)<a href="https://agentmods.dev/skills/aimasteracc/tree-sitter-analyzer/tsa-temporal"><img src="https://agentmods.dev/badge/skills/aimasteracc/tree-sitter-analyzer/tsa-temporal/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-temporal"><img src="https://agentmods.dev/badge/skills/aimasteracc/tree-sitter-analyzer/tsa-temporal.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.00170 | $0.01450 |
| Opus 5.5 | $0.00068 | $0.00580 |
| Sonnet 5.5 | $0.00034 | $0.00290 |
| Haiku 4.5 | $0.00017 | $0.00145 |
Grade A, and why
tsa-temporal 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 1mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tsa-temporal — Hot zones via git history
Per-symbol modification frequency persisted in
ast_symbol_activation. Computed fromgit log --follow -p -U0hunk attribution at index time. Symbols withmod_count_30d >= 5auto-trigger CAUTION inedit action=impact.
When to use
| Goal | How |
|---|---|
| Hot-zone caller fanout | nav action=callers function_name="X" include_activation=true |
| Hot-zone callee fanout | nav action=callees function_name="X" include_activation=true |
| "Is this commit touching hot zones?" | edit action=impact — read risk_factors |
| Single-file recent churn | health action=file — read git_hotspot dim |
Don't use when:
- The question is static (e.g. "who calls X") — use
tsa-graphskill - File is brand new (no git history) — temporal data will be all-zero
Procedure
Pre-refactor hot-zone scan
For each symbol you're about to refactor:
nav action=callers function_name="X" include_activation=true limit=50
Returns enriched entries:
callers: [
{
name: ...,
file: ...,
line: ...,
callee_resolution: ...,
activation: {
mod_count_30d: <int>,
last_modified_at: <unix ts>
}
}, ...
]
Filter mod_count_30d >= 5 to find the callers that have been modified
recently — those are the high-risk integration points for your refactor.
Change-impact gate (catches hot zones automatically)
edit action=impact already includes hot-zone detection. Look for this
in the risk_factors:
risk_factors: [
{
factor: hot_zone | activation,
reason: "hot zone: file_path:symbol modified 12× in 30d, request extra review",
severity: caution
}
]
The verdict bumps to CAUTION when ≥1 changed-file symbol has
mod_count_30d >= 5.
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.
- 1mo ago Changed · +1 lines ca5c2cb1b242
- 2mo ago First seen · 169 lines · 170 tokens per session scan A 43f2fa34e79e
tsa-temporal is a skill published in the GitHub repository aimasteracc/tree-sitter-analyzer (61 stars, last pushed today), licensed MIT. It adds 170 tokens to every session and 1,450 once invoked, about $0.0007 per session on Opus 5.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
pr-reviewer
Review a requested pull request, branch diff or completed task against its actual scope, source and checks. Prepare evidence and comments; post or record a human verdict only when explicitly authorized.
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.