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/jimmypaolini/codebase/callidescope-configurenpx skills add JimmyPaolini/codebase --skill callidescope-configuregit clone --depth 1 https://github.com/JimmyPaolini/codebaseWrote 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/jimmypaolini/codebase/callidescope-configure)<a href="https://agentmods.dev/skills/jimmypaolini/codebase/callidescope-configure"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/callidescope-configure.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.04005 |
| Opus 5 | $0.00085 | $0.02003 |
| Sonnet 5 | $0.00034 | $0.00801 |
| Haiku 4.5 | $0.00017 | $0.00400 |
Grade A, and why
callidescope-configure 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 4d 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telling callidescope what to do
Two surfaces, read together on every run: the flags on the command line, and
the callidescope.config.ts they layer over. Neither is complete on its own —
--check names a limit the file has to have set, and a destination in the file
is only written when a flag asks for it.
The two decisions a run makes
Every invocation answers two independent questions, and neither implies the other:
| Question | Answered by |
|---|---|
| What does this run fail on? | --check, a comma-separated set |
| What does this run rewrite? | --write, plus the destinations in the configuration |
A run given neither --write nor --check reports reads no destination and
rewrites none. It traces, prints, and exits. That is what makes a bare run
safe to type inside somebody's checkout, and it is why --check depth on a
pull request leaves every committed report exactly as it found it.
The flags
| Flag | Meaning |
|---|---|
-a, --addresses |
Comma-separated callable addresses, each <file>#<qualified-name>. depth and breadth only. Prompted for when omitted |
--config |
Path to a callidescope.config.ts. Searched for when omitted |
-d, --directories |
Comma-separated project directories to trace, each holding its own tsconfig.json |
-f, --format |
markdown, mermaid, or json, for what it prints. Markdown by default |
--json |
Path to write the machine-readable report to |
-m, --markdown |
Path to splice the markdown block into |
--check |
Fail on a comma-separated set drawn from breadth, depth, and reports |
--write |
Write every configured destination |
--config, --directories, and --format are the three that depth and
breadth also take, and --addresses is theirs alone — it names what to
report on, which a whole-workspace trace never needs. The rest are the whole-workspace command's alone, because
a lookup never writes or compares a destination.
--check takes a set, and the set matters
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.
- 4d ago First seen · 331 lines · 170 tokens per session scan A 4f6f2058e799
callidescope-configure is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed today), licensed MIT. It adds 170 tokens to every session and 4,005 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-09-01.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…