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 yeaight7/agent-powerups --skill repo-mapgit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/repo-map)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/repo-map"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/repo-map/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/yeaight7/agent-powerups/repo-map"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/repo-map.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00412 |
| Opus 5 | $0.00013 | $0.00206 |
| Sonnet 5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
repo-map 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.
What it actually says
Purpose
Produce a structured overview of an unfamiliar codebase before making changes. Prevents wasted effort caused by misunderstanding project layout or entry points.
When to Use
- Starting work on an unfamiliar repository or module.
- Onboarding to a new project before the first edit.
- Locating where a feature lives before implementing or modifying it.
Do not edit code during this skill. Observation only.
Inputs
- Repository path or access to the codebase.
- Optional: specific area of interest (module, feature, data flow).
Workflow
- Identify project root, package manager, and language(s).
- Find main entry points (executables, API handlers, CLI commands).
- Read the smallest set of files needed to explain the architecture.
- Map major modules, their responsibilities, and how data flows between them.
- Flag risky or complex areas (high churn, missing tests, tangled dependencies).
Output
- Project purpose — What it does in one or two sentences.
- Entry points — Where execution starts.
- Main modules — What each major directory or package is responsible for.
- Data flow — How a typical request or operation moves through the system.
- Risky areas — Complex, undertested, or high-coupling zones to approach carefully.
Verification
- No code was edited during this skill
- All major modules identified
- Entry points documented
- Risky areas flagged
Failure Modes
- Premature editing — Do not make changes during mapping. Finish the map first.
- Monorepo confusion — Map each package or app separately if the repo contains multiple independent projects.
- Metaprogramming blind spots — Dynamic languages may have runtime-defined routes or classes. Note these as limitations in the output.
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.
- yesterday First seen · 51 lines · 26 tokens per session scan A ed6de1e98021
repo-map is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 26 tokens to every session and 412 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-14.
Other skills, from other repositories
bootstrap
Onboarding conversation to generate a user profile.
apple-notes
Read Apple Notes content and execute checklist-driven automations in order. Use when a user asks to run tasks from an Apple Note (especially a checklist note like "AGENT TODO LIST"), or to fetch a specific note body for automation.
confetti
Trigger a two-step confetti celebration by opening the Raycast confetti URL and speaking a phrase with the Alex voice. Use when the user asks to run confetti, celebrate, or trigger the confetti sequence.
meetings
Context for working with the Meetings app's data — where a meeting's notes, diagram, transcript-derived tasks, and calendar cache live, what the lifecycle states mean, and how the app's agents are driven. Load when the user asks about a meeting's notes or action items, or when writing/reading files under the meetings…
pto-planning
Check an employee's PTO balance and policy, then plan or submit a time-off request.
mochi-tips
Feature tips catalog for new users. Plan skill loads this to pick a tip during the first week.