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/ssbun/csl-agent-kit/analyze-projectnpx skills add SSBun/csl-agent-kit --skill analyze-projectgit clone --depth 1 https://github.com/SSBun/csl-agent-kitWrote 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/ssbun/csl-agent-kit/analyze-project)<a href="https://agentmods.dev/skills/ssbun/csl-agent-kit/analyze-project"><img src="https://agentmods.dev/badge/skills/ssbun/csl-agent-kit/analyze-project.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.00077 | $0.00931 |
| Opus 5 | $0.00039 | $0.00465 |
| Sonnet 5 | $0.00015 | $0.00186 |
| Haiku 4.5 | $0.00008 | $0.00093 |
Grade A, and why
analyze-project 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 5d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Project
Build one reusable current-state model for one Git project or component; never modify source.
Invocation
/analyze-project [target] [develop]
- Target defaults to cwd. An existing path or uniquely resolved component wins even when named
develop; otherwise finaldevelopis a compatibility alias with no behavioral effect. - Resolve a natural-language component to exactly one repository path. Multiple scopes, candidates, or Git roots require one selection question and zero report writes.
learn,--need, and other extra positionals are not modes; explain the supported invocation and write nothing.- Route quick orientation to
repo-map; route a single behavior question, research, review, audit, teaching, or change planning to the matching capability.
Contract
- Resolve one canonical target and Git root read-only. Reject external symlinks, escapes, unsafe output parents, and non-regular active targets.
- Active paths: project
docs/analysis/project-map.md; directorydocs/analysis/components/dir/<relative-dir>/map.md; filedocs/analysis/components/file/<relative-file>.md. Historicaldocs/analysis/learning/**is immutable archival material, not evidence. - Read
references/report-contract.mdcompletely before analysis; it governs coverage, replacement, freshness, redaction, and publication. - Read applicable project rules, manifests, entry points, source, configuration, and tests. Follow calls, data, events, state ownership, and external boundaries; README proves intent only, and CodeGraph navigates only.
- Model the scope systematically: its purpose and boundaries, major functional responsibilities, and the core working flows that realize its primary value. For a component, include only its internals, direct neighbors, and flows it owns or materially participates in.
- Put nearby source evidence under an
Evidence:label as a Markdown bullet list. Each bullet contains exactly one repository-relativepath#symbol,path#key, or line anchor wrapped in inline code. Never append anchors to prose or place them inside tables. Publish only source-backed claims; if the scope's central responsibility or a core causal boundary cannot be established, ask one focused question and write nothing. - Do not build, test, run the project, install, access the network, or mutate external state without explicit authorization.
What ships with it
4 files 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.
- 5d ago First seen · 42 lines · 77 tokens per session scan A f38e0a0d94eb
analyze-project is a skill published in the GitHub repository SSBun/csl-agent-kit (10 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 931 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…