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 fikrilal/engineering-agent-skills --skill orient-codebasegit clone --depth 1 https://github.com/fikrilal/engineering-agent-skillsWrote 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/fikrilal/engineering-agent-skills/orient-codebase)<a href="https://agentmods.dev/skills/fikrilal/engineering-agent-skills/orient-codebase"><img src="https://agentmods.dev/badge/skills/fikrilal/engineering-agent-skills/orient-codebase/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/fikrilal/engineering-agent-skills/orient-codebase"><img src="https://agentmods.dev/badge/skills/fikrilal/engineering-agent-skills/orient-codebase.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.00059 | $0.00538 |
| Opus 5.5 | $0.00024 | $0.00215 |
| Sonnet 5.5 | $0.00012 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
orient-codebase 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 2mo 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orient Codebase
Build an evidence-grounded map that helps the learner reason about the system. Do not produce an exhaustive file inventory.
Workflow
- Establish the learner context from the conversation. Identify known languages, frameworks, and architectural patterns. Ask only when missing context would materially change the explanation.
- Read repository instructions and source-of-truth documents first. Then inspect manifests, build scripts, CI, entry points, and the top-level tree.
- Identify the product shape, deployed processes, runtime boundaries, persistence, external systems, and primary user workflows.
- Trace at least one representative vertical path from entry point to observable result. Use this path to make abstract boundaries concrete.
- Distinguish architectural intent documented by the repository from structure inferred from code.
- Identify only the highest-leverage reading targets and material uncertainties.
- Stop once the learner has a useful map. Offer deeper exploration by workflow or module instead of front-loading every detail.
Output
Default to this compact shape:
- System in one paragraph: what it does and how it runs.
- System map: major boundaries and where state lives, using a short list or text diagram.
- Start here: three to five files or workflows that build the mental model fastest.
Include a representative workflow when it makes the map easier to understand. Leave build commands, exhaustive module lists, documentation drift, and deeper risks for follow-up unless they are essential.
Explanation Rules
- Ground important claims in source files, configuration, tests, or recorded command output.
- Use file and line references when the client supports them.
- Start with purpose and observable behavior, then reveal implementation detail.
- Adapt explanations to knowledge already stated by the learner.
- Use plain words and short sentences. Give the answer before supporting detail.
- State uncertainty only when it changes the mental model.
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.
- 2mo ago First seen · 48 lines · 59 tokens per session scan A bc3e542b43c1
orient-codebase is a skill published in the GitHub repository fikrilal/engineering-agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 538 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
ci-fixer
CI failures - read error, minimal fix, verify.
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…