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/chinkan/rustfox/codebase-gap-analysisnpx skills add chinkan/RustFox --skill codebase-gap-analysisgit clone --depth 1 https://github.com/chinkan/RustFoxWhat 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.00023 | $0.00437 |
| Opus 5 | $0.00012 | $0.00218 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
codebase-gap-analysis 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 yesterday.
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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Gap Analysis vs Reference Architecture
Use when the user wants to deeply compare their project or codebase against a reference implementation, framework, or architectural pattern to find gaps and improvement opportunities.
Workflow
1. Define Scope & Dimensions
- Confirm the user's project location (repo URL, local path, or pasted code).
- Confirm the reference target (technology, product, or architectural pattern).
- Select comparison dimensions relevant to the domain (e.g., orchestration, memory, concurrency, skills, backends, observability, agent lifecycle).
2. Explore User Codebase
- Fetch repository metadata and directory structure.
- Read root configuration and documentation files.
- Dive into core source directories to map the architecture.
- Identify and read critical modules (planner, orchestrator, supervisor, memory, tools, agents, config).
- Summarize current capabilities, abstractions, and design patterns found.
3. Research Reference Architecture
- Search official documentation, repositories, and technical articles for the reference system.
- Extract concrete capabilities, configuration mechanisms, and architectural layers.
- Note any experimental, undocumented, or advanced features relevant to the comparison.
4. Execute Structured Comparison
- Build a side-by-side comparison table across the chosen dimensions.
- Flag capabilities present in the reference but missing or incomplete in the user's project.
- Note areas where the user's project may be ahead, equivalent, or intentionally divergent.
5. Prioritized Recommendations
- List each gap with: description, impact, and suggested implementation approach aligned with the user's stack.
- Assign priority (Critical / High / Medium / Low).
- Propose a pragmatic roadmap that respects existing dependencies and build patterns.
6. Deliver Synthesis
- Provide an overall architectural maturity assessment.
- Highlight quick wins versus long-term investments.
- Offer to elaborate on, design, or implement any specific recommendation.
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.
- yesterday First seen · 44 lines · 23 tokens per session scan A 784e5725ae03
codebase-gap-analysis is a skill published in the GitHub repository chinkan/RustFox (6 stars, last pushed 25d ago), licensed MIT. It adds 23 tokens to every session and 437 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-31.
Other skills, from other repositories
codebase-onboarding
Use when you land in an unfamiliar or inherited codebase and must get productive fast: a breadth-first map of entry points, request flow, module ownership, hidden side effects (cron, webhooks, workers) and churn hotspots, committed as CODEBASE-MAP.md. NOT a deep audit of one module (that is analyze) or chasing one…
repository-discovery
Use this skill to systematically explore an unfamiliar codebase before making any changes. Activates when starting work in an unknown repository, adding a new feature, debugging without prior context, or when no CONTEXT.md exists. Produces a grounded understanding of architecture, conventions, and constraints.
compare-embedding-models
Run an apples-to-apples benchmark of two embedding models on a fixture or your KB and produce an HTML report covering cold-start indexing, warm-query latency, batch throughput, storage, and quality.
subsystem-map
This skill should be used before answering "does Genesis have X", "does Genesis lack X", auditing Genesis capabilities, comparing Genesis to an external system, or reviewing/summarizing the architecture. It routes to the canonical judgment-layer subsystem map so audits start from the map, not from a cold grep. Also…
archlang
Use when the user wants to create, edit, or inspect an architectural floor plan / building layout as code — e.g. "draw a 2-bedroom apartment", "add a bathroom to this plan", "make the bedroom 1 m wider", "lay out an office floor". ArchLang is a tiny text language that compiles a .arch file to a professional floor-plan…
Architecture Diagram
Produces clean architecture and system diagrams from actual repo or product truth instead of decorative boxes.