repo-context

repo-context is a skill for Claude Code from DefaultPerson/agent-setup. It costs 23 tokens per session (674 once invoked), scanned A, original, MIT.

A compact snapshot of a repository's structure, technology markers, documentation, Git state, and recent activity for an agent to use as context.

In plain words
What is it for?
Use it when starting work in an unfamiliar repository to understand its files, tools, instructions, current changes, and recent commits.
Why use it?
It gives the agent essential project information without repeatedly scanning the repository or making assumptions about its setup.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; positional $N argument; mentions AGENTS.md.

Good fit Use it when starting work in an unfamiliar repository to understand its files, tools, instructions, current changes, and recent commits.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/defaultperson/agent-setup/repo-context
Install

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.

Any agent
npx skills add DefaultPerson/agent-setup --skill repo-context
Clone the repo
git clone --depth 1 https://github.com/DefaultPerson/agent-setup

Made for: Claude Code.

Wrote 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.

agentmods badge for repo-context

README.md
[![agentmods](https://agentmods.dev/badge/skills/defaultperson/agent-setup/repo-context/github.svg)](https://agentmods.dev/skills/defaultperson/agent-setup/repo-context)
Your own site
<a href="https://agentmods.dev/skills/defaultperson/agent-setup/repo-context"><img src="https://agentmods.dev/badge/skills/defaultperson/agent-setup/repo-context/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.

agentmods 80×15 button for repo-context

Your own site · 80×15
<a href="https://agentmods.dev/skills/defaultperson/agent-setup/repo-context"><img src="https://agentmods.dev/badge/skills/defaultperson/agent-setup/repo-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 674 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00674
Opus 5 $0.00012 $0.00337
Sonnet 5 $0.00005 $0.00135
Haiku 4.5 $0.00002 $0.00067

Measured yesterday against content hash bbb9177e8b2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

repo-context 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.

.claude/skills/repo-context/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repo context

The snapshot below was collected before this prompt reached you. Treat it as ground truth and do not re-run these commands.

Snapshot

Root: !git rev-parse --show-toplevel 2>&1 | head -1

Git status:

git status -sb 2>&1 | head -15

Tracked files (total, then per top-level directory):

git ls-files 2>/dev/null | wc -l
git ls-files 2>/dev/null | awk -F/ 'NF>1{print $1}' | sort | uniq -c | sort -rn | head -25

File list (first 150):

git ls-files 2>/dev/null | head -150

Stack markers present:

ls -1d package.json pyproject.toml go.mod Cargo.toml requirements.txt uv.lock pnpm-lock.yaml Dockerfile docker-compose.yml compose.yaml Makefile .github/workflows 2>/dev/null || true

README (first 80 lines):

head -80 README.md 2>/dev/null || echo "(no README.md)"

AGENTS.md (first 60 lines):

head -60 AGENTS.md 2>/dev/null || echo "(no AGENTS.md)"

Recent activity:

git log --oneline -15 2>&1 | head -15
git diff --stat HEAD~5..HEAD 2>/dev/null | tail -15

Task

  1. Use the snapshot for structure, stack and recent activity. CLAUDE.md is already loaded — don't re-read it.
  2. Read at most 5 key files: entry points, core models/schemas, main config. Pick them from the file list; skip lockfiles, generated and vendored code.
  3. If the snapshot shows this is not a git repository, fall back to a top-level ls and the README.
  4. Output the summary below — bullets, no walls of text.

Output

## Project Context

### Overview
- **Purpose**: {what this project does}
- **Tech Stack**: {languages, frameworks, key deps}

### Architecture
- **Structure**: {key directories, patterns}
- **Entry Points**: {main files}
- **Config**: {build tools, CI/CD, infra}

### Current State
- **Branch**: {current branch}
- **Recent Work**: {last 5 commits, one line each}
- **Active Areas**: {most changed files/dirs}

### Key Files
- {path} — {purpose}

Read the full file on GitHub · 84 lines

Changes

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.

  1. yesterday First seen · 84 lines · 23 tokens per session scan A bbb9177e8b2f

Subscribe to this mod's changes

repo-context is a skill published in the GitHub repository DefaultPerson/agent-setup (11 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 674 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.

Related

Other skills, from other repositories

chronos

Gives coding agents temporal awareness by reading the session transcript the host already writes, so the agent stops guessing about time and stops repeating commands that just failed. Activates whenever an agent reasons about recency, elapsed time, retry windows, deploy cooldowns, memory or file staleness, idle…

OthmanAdi/chronos · 92 tokens

decision-ledger

Maintain an append-only decision ledger (DECISIONS.md). Use when the user confirms a decision, reverses or changes a past decision, asks what was decided and why, or at session start to load standing decisions.

svy04/ballast · 48 tokens

pin

Turn a correction or working preference the user just expressed into a permanent ballast rule. Use when the user corrects your behavior, says "don't do X" / "always do Y" / "I told you before", or asks you to remember how they want things done.

svy04/ballast · 57 tokens

knowledge-base

Keep verified findings in memory/knowledge/ so the same research is never done twice. Use before researching any topic, when a finding passes the verify gate, or when about to answer from something learned in an earlier session.

svy04/ballast · 47 tokens

catchup

Restore context after /clear by summarizing recent work and project state.

FlorianBruniaux/claude-code-plugins · 16 tokens

recall

Sweep everything the project already holds before answering — at the first message of a session, and again whenever the subject shifts to something the current thread was not about. Use before replying, not only before researching.

svy04/ballast · 44 tokens