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/kaka-cheaper/codesee/templatesnpx skills add Kaka-cheaper/codeSee --skill templatesgit clone --depth 1 https://github.com/Kaka-cheaper/codeSeeWhat 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.00088 | $0.01101 |
| Opus 5 | $0.00044 | $0.00550 |
| Sonnet 5 | $0.00018 | $0.00220 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
codesee 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 3d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeSee Skill
Keep .codesee/features.json in sync with the project's actual functionality. The graph captures what the project does, not how, at three levels: Epic → Feature → Step.
When to activate
- The user says "scan", "sync codesee", "refresh feature map", "更新功能图", or similar
- After completing a code change in a project that has
.codesee/orAGENTS.mdmentioning CodeSee - When
.codesee/features.jsonis missing/empty in a project that should have it
Quick decision tree
1. Is .codesee/features.json missing or empty?
YES → Run first-time scan: read .codesee/prompts/scan.md
NO → Continue to step 2
2. Did you just complete a code change?
YES → Run incremental sync: read .codesee/prompts/sync.md
NO → Continue to step 3
3. Did the user explicitly ask to refresh?
YES → Read .codesee/prompts/scan.md (force re-scan)
NO → Skip activation
Project-stage awareness
scan.md auto-detects which sub-mode to use:
- SDD project (has
.specify/,.trellis/,.bmad-core/,.agents/skills/) →scan-sdd.md(forward projection from spec/PRD) - Code-only light (< 100 source files) →
scan-light.md - Code-only heavy (≥ 100 source files) →
scan-heavy.md(4-phase) - Doc-only / planning (no code yet) →
scan-planning.md
Don't pick the sub-mode yourself. Read scan.md first; it routes for you.
Hard constraints (MUST)
- Never modify files under
.codesee/prompts/or.codesee/scripts/ - Never modify a feature with
locked: true - Never rename existing IDs (deprecate via
tags: ['deprecated']instead) - Always run
node .codesee/scripts/validate-features.mjsafter writing — exit code 1 must be fixed flow.kindis required on every flow edgestep.namemust be a verb phrase in the language specified bymanifest.lang
See .codesee/prompts/_rules.md for the full constraint hierarchy (MUST / SHOULD / MAY).
Checkpoint protocol (large tasks)
If the user's task touches 5+ files, don't wait until the end to sync. Split into logical closures (a "closure" = a user-perceivable, independently verifiable feature) and run sync.md after each. After all closures done, do a final integrity check (coverage / relations / epic_flow / refs / validator). See .codesee/prompts/sync.md § Checkpoint protocol.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 85 lines · 88 tokens per session scan A 394ba77009ac
codesee is a skill published in the GitHub repository Kaka-cheaper/codeSee (47 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,101 once invoked, about $0.0004 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
infographic-creator
基于给定文字内容创建精美信息图。当用户请求创建信息图时使用。.
data-viz-renderer
Generate self-contained HTML/SVG infographics from JSON data, including stat cards, bar charts, flow diagrams, and mixed dashboards. Offers 8 color palettes and built-in icons with no external dependencies. Triggered when users request data visualization, infographics, charts, or dashboards.
code-to-diagram
Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts. Uses AST parsing to map import dependencies for Python, JS/TS, Go, and Java, outputting Mermaid or SVG files. Triggered when users ask to visualize code architecture, understand dependencies, draw a flowchart, or create a…
canvas-chart
Canvas chart rendering skill. Teaches the agent to output DOJOCHART blocks for rendering interactive ECharts visualizations in the Dashboard Canvas panel.
blog-post
Author a new entry for the Semiotic blog. Use this skill whenever the user asks for a blog post, release summary, chart explainer, or case study to publish at /blog/SLUG.
review
Structured PR review for pygraphistry. Input: PR number/branch (default current branch PR). Output: findings and convergence artifacts under plans/ /. Method: multi-wave, evidence-first review across spec, correctness, tests, security, code quality, DRY, concurrency, performance, architecture, operability, and…