copcon

Generate a token-counted codebase snapshot with token totals and file-type distribution.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/KAFKA2306/yt3 --skill copcon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copcon
Source: https://github.com/KAFKA2306/yt3/tree/main/.agent/skills/copcon
Command: npx skills add https://github.com/KAFKA2306/yt3 --skill copcon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reproducible, token-aware snapshot of a codebase so LLMs and agents can consume a bounded, measured context instead of attempting to ingest unbounded repository content.

Core Features & Use Cases

  • Token-counted context: Produces a token-aware report that quantifies how much of the repository fits within an LLM budget.
  • Shareable output: Writes a single output file (copcon/context.md) that other agents or reviewers can consume.
  • Usage scenarios: Prepare repository context for agent handoffs, audit token-heavy files for .copconignore, or include a git diff for reviewing uncommitted changes.

Quick Start

Use copcon to generate a token-counted codebase context and save the results to copcon/context.md for LLM consumption.

Frequently Asked Questions about copcon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I count tokens in a codebase for LLM context?

Counting tokens in a codebase for LLM context involves generating a snapshot that quantifies total counts and file-type distribution. This creates a bounded report so repository content fits within specific model limits.

What is the best way to share codebase context between AI agents?

Sharing codebase context between agents is best done by generating a single output file like copcon/context.md. This reproducible file provides a measured, token-aware snapshot that downstream agents can directly consume.

How do I include a git diff when generating a codebase summary?

Including a git diff when generating a codebase summary requires using the git diff inclusion option during snapshot generation. This captures uncommitted changes alongside the token-counted repository context for comprehensive LLM review.

Can I exclude specific files from my token budget audit?

You can exclude specific files from a token budget audit using exclusion rules and a .copconignore file. This filters out token-heavy files, ensuring the generated context snapshot stays within strict LLM limits.

Does copcon support limiting traversal depth for large repositories?

Copcon supports limiting traversal depth for large repositories. By setting the traversal depth option, you restrict directory scanning to produce a bounded, size-aware context snapshot tailored to your needs.