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/giauphan/codeatlas-platform/codeatlas-verifynpx skills add giauphan/codeatlas-platform --skill codeatlas-verifygit clone --depth 1 https://github.com/giauphan/codeatlas-platformWhat 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.00017 | $0.00920 |
| Opus 5 | $0.00009 | $0.00460 |
| Sonnet 5 | $0.00003 | $0.00184 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
codeatlas-verify 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 2d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeAtlas Verification
Run checks relevant to changed code:
pnpm run build
pnpm test
git diff --check
git status --short
For dashboard changes, also run from dashboard/:
pnpm install --frozen-lockfile
pnpm run build
pnpm test
Do not claim success if a check fails or was skipped. Do not modify unrelated files while fixing verification failures.
Pipeline verification gates (CI parity)
Features and refactors now ship through a strict CI pipeline. Match these gates locally before finishing so CI stays green:
- Root gates:
pnpm run typecheck,pnpm run build,pnpm test(Node built-in test runner). - Dashboard gates:
cd dashboard && pnpm run typecheck,pnpm run build,pnpm test(vitest). - Dashboard TypeScript is
strict: truewithnoFallthroughCasesInSwitch. Unused-symbol checks (noUnusedLocals/noUnusedParameters) are intentionally off because pre-existing unused locals are widespread; do not re-enable them unless you also clean up every affected component. - Dashboard tests require jsdom 29 and
undici@^7(pnpm-workspace.yamloverride isundici: ^7.25.0). Never pin undici below 7; jsdom 29 importsundici/lib/handler/wrap-handler.js, which does not exist in undici 6. - CI security job runs
pnpm audit --prod --audit-level=highand gitleaks with nocontinue-on-error. Never put key-shaped strings in tests or fixtures (e.g.ca_test_key_12345was caught by gitleaks); use innocuous placeholders liketest-token. - CI jobs: build (root + dashboard typecheck/build/tests), sqlite (
CODEATLAS_DB_TYPE=sqlite,CODEATLAS_SQLITE_PATHunder the workspace), context-hygiene (tests/unit/context-hygiene.test.ts), security (audit + gitleaks). Workflow has concurrency cancellation and least-privilege permissions.
Context-hygiene gate
A strict CI job (context-hygiene) runs tests/unit/context-hygiene.test.ts in isolation. It guards the retrieval inject-gate — the last filter before Second Brain memories reach a Claude prompt — against the content that previously leaked into live sessions.
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.
- 2d ago First seen · 57 lines · 17 tokens per session scan A 4c50721fb85f
codeatlas-verify is a skill published in the GitHub repository giauphan/codeatlas-platform (11 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 920 once invoked, about $0.0001 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
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.