Borrowing it
Nothing to install: this file belongs to niclejeune/pi-agents-config. 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/niclejeune/pi-agents-config/main/.pi/agent/skills/repotrace/SKILL.mdgit clone --depth 1 https://github.com/niclejeune/pi-agents-configWrote 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/niclejeune/pi-agents-config/repotrace)<a href="https://agentmods.dev/skills/niclejeune/pi-agents-config/repotrace"><img src="https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/repotrace/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/niclejeune/pi-agents-config/repotrace"><img src="https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/repotrace.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.00049 | $0.00619 |
| Opus 5 | $0.00024 | $0.00309 |
| Sonnet 5 | $0.00010 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
repotrace 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 12d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repotrace Skill
Use repotrace as the default local code intelligence layer for repositories. It is a CLI that works with any coding agent; this workflow uses it with pi agents.
Public repo: https://github.com/niclejeune/repotrace
When to use
Use this before reading many files or making nontrivial code changes:
- entering an unfamiliar repo
- implementing a feature touching multiple files
- debugging unclear behavior
- reviewing impact/blast radius
- checking architecture risk before edits
- finding symbols, callers, callees, routes, or dependency cycles
- generating a small context bundle for a worker/subagent
Do not bulk-read the repo first when repotrace can give a focused map.
Default workflow
From the target repository root:
repotrace index .
repotrace check --no-fail
repotrace context "<task description>" --print
Only read the files listed in the bundle first. Widen scope only after a concrete reason appears.
Common commands
repotrace overview
repotrace find <query>
repotrace symbol <name>
repotrace callers <symbol>
repotrace callers <symbol> --broad
repotrace callees <symbol>
repotrace file <path>
repotrace impact <file-or-symbol>
repotrace routes
repotrace deps
repotrace cycles
repotrace check --no-fail
repotrace changed --since main
Use global JSON before the subcommand:
repotrace --json check --no-fail
repotrace --json context "<task>" --print
How to interpret checks
repotrace check currently flags:
error: Python import cycleserror: production code importing test codewarning: large production fileswarning: high fan-in production modules
Warnings are not automatic blockers, but they mean edits need more care and likely tests.
Agent behavior rule
For any nontrivial code task, prefer this sequence:
repotrace index .repotrace check --no-failrepotrace context "<task>" --print- Read only the listed files first.
- Use
repotrace callers,callees,impact,deps, orcyclesbefore widening context. - Report any
checkerrors/warnings that affect the task.
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.
- 12d ago First seen · 88 lines · 49 tokens per session scan A 5f136cc305c8
repotrace is a skill published in the GitHub repository niclejeune/pi-agents-config (1 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 619 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
improve-codebase-architecture
Find AI-readiness architecture issues and module-deepening refactors. Use when improving codebase architecture, testability, agent navigation, seams, or refactor tickets.
techdebt-finder
Find technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities.
deslop
Clean AI-generated code noise. Use when reviewing diffs, removing unnecessary comments, tightening verbose code, or desloping recent changes.
critique-theater
Five-dimension design quality review — score the artifact against craft, brand, accessibility, and copy, then fix what falls short before handing it over.
vibe-review
Review a proposed change against requirements, regressions, verification evidence, and relevant security risks.
code-refiner
Deep code simplification and refactoring preserving behavior across Python, Go, TypeScript, Rust. Targets complexity, anti-patterns, readability debt. Triggers on: "simplify this code", "refactor for clarity", "reduce complexity", "make this more readable", "tech debt cleanup", "too much nesting".