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/aimasteracc/tree-sitter-analyzer/tsa-temporalnpx skills add aimasteracc/tree-sitter-analyzer --skill tsa-temporalgit 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.svg" alt="Measured on agentmods" 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 | $0.00170 | $0.01423 |
| Opus 5 | $0.00085 | $0.00711 |
| Sonnet 5 | $0.00034 | $0.00285 |
| Haiku 4.5 | $0.00017 | $0.00142 |
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 5d 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 — 169 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.
- 5d 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 (48 stars, last pushed yesterday), licensed MIT. It adds 170 tokens to every session and 1,423 once invoked, about $0.0009 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
context7-docs
Fetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service. Use whenever the user asks about a specific library — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot — because training data may not reflect recent API changes or…
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…
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…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
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 BitFun's unified Review mechanism instead.…
miniapp-dev
Develops, maintains, and generates BitFun MiniApps (Zero-Dialect Runtime). Use when (1) working on miniapp framework code under src/crates/assembly/core/src/miniapp/ or src/web-ui/src/app/scenes/miniapps/; or (2) generating / creating / designing a NEW MiniApp for the user — including any request like "做一个小应用 / 生成…