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-implementnpx skills add giauphan/codeatlas-platform --skill codeatlas-implementgit 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.00794 |
| Opus 5 | $0.00009 | $0.00397 |
| Sonnet 5 | $0.00003 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
codeatlas-implement 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeAtlas Implementation
-
Run
git status --short. -
Identify feature entry points with CodeAtlas MCP
trace_feature_floworsearch_entitieswhen available. -
Read related source, dependencies, and tests.
-
Choose the smallest change that satisfies the request.
-
Keep HTTP/MCP code in
src/presentation, business logic insrc/services, and persistence insrc/databaseor repositories. -
Use SQLite +
sqlite-vecas default behavior. Do not make PostgreSQL required for local work. -
Add regression coverage for changed behavior.
-
Run:
pnpm run build pnpm test -
Review
git diff --checkand final diff. -
Call
sync_system_memorywith a concise change description.
Do not reset, clean, stash, commit, push, or alter unrelated files. Report any unavailable or failing check.
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), security (audit + gitleaks). Workflow has concurrency cancellation and least-privilege permissions.
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 · 48 lines · 17 tokens per session scan A 3c4a3b2290ca
codeatlas-implement 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 794 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…