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-indexergit 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-indexer)<a href="https://agentmods.dev/skills/nitinbhide/tcaitoolkit/repo-indexer"><img src="https://agentmods.dev/badge/skills/nitinbhide/tcaitoolkit/repo-indexer.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.1 | $0.00025 | $0.01392 |
| Opus 5 | $0.00013 | $0.00696 |
| Sonnet 5 | $0.00005 | $0.00278 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
repo-indexer 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 4d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Repository Indexer Skill
Purpose
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 used by coding agents for project decision making.
The skill generates documentation that may target coding agents; this skill itself does not perform coding-agent decision workflows.
DO NOT deviate from this SKILL instructions.
Inputs
- Root directory path of the local repository.
Outputs
- Markdown index files written directly into each folder of the repository.
- The root index file must be generated using
rootdocmap_tmpl.md. - All folder-level index files must be generated using
folderdocmap_tmpl.md.
Behavior
The skill performs a recursive scan of the repository and generates index files containing:
- YAML frontmatter metadata
- Folder-level summary (4–5 lines)
- File listings with short summaries
- Semantic tags
- TODO / FIXME / NOTE detections
- Child folder references
- Dependency graph generation is disabled for now
- Use the templates defined in this skills
references/folder only
Template Usage
-
Root Index File (
DOCMAP.md)
Must be generated using the template defined inrootdocmap_tmpl.md -
Folder Index Files (
docmap.md)
Must be generated using the template defined infolderdocmap_tmpl.md
The skill must fill these templates with actual repository data.
Root Index Requirements
The root DOCMAP.md must include a section explaining:
- how the index hierarchy is organized
- how AI coding agents should use the index
(The actual instruction text is defined inside rootdocmap_tmpl.md.)
File/Folder Inclusion/Exclusion Rules
Included File Types
- Source code (any language)
- Design documents
- Architecture documents and Architecture Decision Records (ADR)
- Specification documents
- Test plans and test cases
- Implementation plans
- SQL files
- Protobuf schema files
- Markdown (
.md), text, Restructured Text (.rst)
What ships with it
2 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.
- 4d ago Changed · +32 lines · +5 tokens per session db671b4238b8
- 8d ago First seen · 114 lines · 20 tokens per session scan A 40ecc50380fa
repo-indexer is a skill published in the GitHub repository nitinbhide/tcaitoolkit (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,392 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
agents-generator
Generate project-specific AGENTS.md and companion rules by analyzing a codebase. Supports full, minimal, update, and dry-run modes with package-manager detection, monorepos, backups, managed blocks, confidence scoring, and command validation.
cocoindex
This skill should be used when building data processing pipelines with CocoIndex, a Python library for incremental data transformation. Use when the task involves processing files/data into databases, creating vector embeddings, building knowledge graphs, ETL workflows, or any data pipeline requiring automatic change…
target-connector
This skill should be used when creating a new target connector for CocoIndex to integrate with external systems. It provides guidance on implementing TargetHandler, TargetActionSink, and related types for declarative target state synchronization with change detection and automatic cleanup.
cocoindex-diagrams
This skill should be used when creating, editing, or reviewing inline SVG diagrams for the CocoIndex docs site (anything under docs/src/content/docs/). It encodes the component-based primitive system under docs/src/components/diagrams/, the palette + shape semantics, the preview-and-verify loop using headless Chrome…
upgrade-examples
This skill should be used when upgrading the cocoindex package version in all example pyproject.toml files. It uses regex-based sed commands to efficiently update version constraints across multiple files at once.
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the…