repository-discovery

repository-discovery is a skill for Claude Code, Codex from Stivi7/cyberpunk-context-runners. It costs 23 tokens per session (238 once invoked), scanned A, original, MIT.

A repository-inspection workflow for projects whose technology, commands, conventions, or boundaries are unknown or outdated. It builds a project map from files, configuration, automation, history, and representative code.

In plain words
What is it for?
It helps identify the project stack and structure, record available commands and conventions, mark unknowns, and separate observed facts from recommendations and existing failures.
Why use it?
It prevents recommendations and verification steps from relying on guessed commands or stale assumptions about the codebase.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps identify the project stack and structure, record available commands and conventions, mark unknowns, and separate observed facts from recommendations and existing failures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stivi7/cyberpunk-context-runners/repository-discovery
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 Stivi7/cyberpunk-context-runners --skill repository-discovery
Clone the repo
git clone --depth 1 https://github.com/Stivi7/cyberpunk-context-runners

Made for: Claude Code, Codex.

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 repository-discovery

README.md
[![agentmods](https://agentmods.dev/badge/skills/stivi7/cyberpunk-context-runners/repository-discovery/github.svg)](https://agentmods.dev/skills/stivi7/cyberpunk-context-runners/repository-discovery)
Your own site
<a href="https://agentmods.dev/skills/stivi7/cyberpunk-context-runners/repository-discovery"><img src="https://agentmods.dev/badge/skills/stivi7/cyberpunk-context-runners/repository-discovery/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 repository-discovery

Your own site · 80×15
<a href="https://agentmods.dev/skills/stivi7/cyberpunk-context-runners/repository-discovery"><img src="https://agentmods.dev/badge/skills/stivi7/cyberpunk-context-runners/repository-discovery.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 238 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.00238
Opus 5 $0.00012 $0.00119
Sonnet 5 $0.00005 $0.00048
Haiku 4.5 $0.00002 $0.00024

Measured 11d ago against content hash c73f8e168161, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

repository-discovery 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 11d 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.

templates/skills/core/repository-discovery/SKILL.md · 38 lines

What it actually says

Repository Discovery

Metadata

  • Version: 1.0.0
  • Triggers: New project, stale context, unfamiliar area, or contradictory evidence
  • Allowed agents: Operator
  • Side effects: Updates tracked project context

When to Use

Use before standards or verification commands are inferred. Skip a full rescan when current evidence already covers the task area.

Inputs

Repository tree, guidance files, dependency manifests, build configuration, automation, representative code, history, and task scope.

Procedure

  1. Inspect relevant files before making recommendations.
  2. Record observed stack, structure, conventions, dependencies, and protected areas.
  3. Derive command categories from repository documentation and automation.
  4. Mark missing categories unavailable instead of inventing commands.
  5. Separate facts, recommendations, unknowns, and baseline failures.

Verification

Link important facts to repository evidence and confirm recorded commands match the project's own sources.

Output

Updated project map, command registry, conventions, boundaries, unknowns, and baseline failures.

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. 11d ago First seen · 38 lines · 23 tokens per session scan A c73f8e168161

Subscribe to this mod's changes

repository-discovery is a skill published in the GitHub repository Stivi7/cyberpunk-context-runners (4 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 238 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens