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 nimadorostkar/Claude-Skills-collection --skill repository-explorationgit clone --depth 1 https://github.com/nimadorostkar/Claude-Skills-collectionWrote 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/nimadorostkar/claude-skills-collection/repository-exploration)<a href="https://agentmods.dev/skills/nimadorostkar/claude-skills-collection/repository-exploration"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/repository-exploration/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/nimadorostkar/claude-skills-collection/repository-exploration"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/repository-exploration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01062 |
| Opus 5 | $0.00023 | $0.00531 |
| Sonnet 5 | $0.00009 | $0.00212 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
repository-exploration 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 12d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Exploration
Purpose
Build an accurate mental model of an unfamiliar codebase quickly, so the first change you make fits the system instead of fighting it.
When to Use
- Joining a project or inheriting a service.
- Before making a first change to a repository you do not know.
- Auditing a codebase before acquisition, handover, or a major decision.
- Writing or refreshing a
CLAUDE.md/ onboarding document.
Capabilities
- Entry-point discovery and request-path tracing.
- Dependency and module mapping.
- Convention detection: how this codebase does errors, config, tests, logging.
- Identification of hotspots: files with the highest churn and the most authors.
- Detection of dead code, duplicated logic, and abandoned migrations.
Inputs
- The repository, with full git history.
- Build and run instructions, if they exist.
- Any existing documentation, treated as a hypothesis rather than fact.
Outputs
- A map: entry points, layers, data stores, external dependencies.
- The conventions a new change must follow.
- A list of the riskiest areas and why.
- Concrete questions that the code cannot answer.
Workflow
- Read the boundaries first —
README, build files, CI config,Dockerfile, deployment manifests. These tell you what runs, how, and against what. - Find the entry points — HTTP routes, CLI commands, queue consumers, cron entries,
mainfunctions. Everything else is reachable from one of them. - Trace one request end to end — Pick the most representative operation and follow it from entry to data store and back. This single trace teaches you the layering, the error convention, and the persistence pattern at once.
- Detect the conventions — Read three files from the same layer. What is common is the convention; what is unique is either newer, older, or a mistake.
- Find the churn —
git log --format=%an --name-onlyaggregated by file. High churn plus many authors marks the code that will be hardest and most important to understand. - Run the tests — What they cover tells you what the team is afraid of breaking.
- Write it down — A map that lives in the repository, so nobody has to do this again.
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.
- 12d ago First seen · 102 lines · 46 tokens per session scan A 65c16282a210
repository-exploration is a skill published in the GitHub repository nimadorostkar/Claude-Skills-collection (26 stars, last pushed 25d ago), licensed MIT. It adds 46 tokens to every session and 1,062 once invoked, about $0.0002 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-30.
Other skills, from other repositories
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.
offensive-wifi
Wireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".