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 skills add nitinbhide/tcaitoolkit --skill repo-navgit clone --depth 1 https://github.com/nitinbhide/tcaitoolkitWrote 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/nitinbhide/tcaitoolkit/repo-nav)<a href="https://agentmods.dev/skills/nitinbhide/tcaitoolkit/repo-nav"><img src="https://agentmods.dev/badge/skills/nitinbhide/tcaitoolkit/repo-nav/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nitinbhide/tcaitoolkit/repo-nav"><img src="https://agentmods.dev/badge/skills/nitinbhide/tcaitoolkit/repo-nav.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00028 | $0.03108 |
| Opus 5 | $0.00014 | $0.01554 |
| Sonnet 5 | $0.00006 | $0.00622 |
| Haiku 4.5 | $0.00003 | $0.00311 |
Grade A, and why
repo-nav 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 today.
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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Repository Navigation Index Generation Skill
Purpose
Analyze a software repository and generate a hierarchy of index files that enables AI coding agents to rapidly understand the repository structure, architecture, implementation details, business features, dependencies, and change impact.
Generate Markdown index files (DOCMAP.md at root, docmap.md in each folder) that summarize the contents of a local repository using progressive disclosure.
This skill only generates index files and is not to be used by coding agents for project decision making.
Progressive Disclosure principle:
- A coding agent should be able to understand the repository at a high level by reading a small number of files.
- The agent should be guided toward the most relevant folders and files.
- Detailed information should only appear at deeper levels of the hierarchy.
- Each index/docmap should help the agent decide what to read next.
- Each index should help the agent decide what files are likely to require modification.
- Each child index must provide greater detail than its parent.
- Each parent index must summarize child content.
The primary consumers of the generated indexes are AI coding agents.
DO NOT deviate from this SKILL instructions during the execution of the repo-nav workflow.
Scope and boundaries
This skill applies only to the explicitly invoked repo-nav workflow for generating or updating DOCMAP.md and docmap.md files. It is not a general project workflow, coding standard, or replacement for project-wide rules in AGENTS.md.
Objectives
The generated indexes/docmap shall help agents:
- Understand repository architecture
- Understand major business capabilities
- Locate implementation areas
- Understand technology stacks
- Understand dependencies
- Locate related tests
- Locate related specifications
- Evaluate change impact
- Determine which files to read
- Determine which files to modify
- Avoid unnecessary repository exploration
What ships with it
3 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.
- today Changed · +18 lines c438fff12419
- yesterday Changed · +71 lines 665115996718
- 2d ago First seen · 252 lines · 28 tokens per session scan A 5d07e4f327a0
repo-nav is a skill published in the GitHub repository nitinbhide/tcaitoolkit (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 3,108 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-09-11.
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…
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…
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…
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…