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 agentmods add skills/jcottam/agent-resources/orientnpx skills add jcottam/agent-resources --skill orientgit clone --depth 1 https://github.com/jcottam/agent-resourcesWhat 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 | $0.00096 | $0.02184 |
| Opus 5 | $0.00048 | $0.01092 |
| Sonnet 5 | $0.00019 | $0.00437 |
| Haiku 4.5 | $0.00010 | $0.00218 |
Grade A, and why
orient 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 2d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orient
Systematically explore a codebase and produce a structured orientation that tells a developer everything they need to start working productively. Depth scales with project size — small projects get a tight summary, large projects get a layered map.
Phase 1 — Project Identity
Establish what the project is before reading any source code.
Read top-level files (in order of priority)
README.md/README— stated purpose, setup instructions, feature listAGENTS.md— architecture boundaries, "always do / never do" rules.cursor/rules/— workspace conventions for this project- Manifest file —
package.json,pyproject.toml,Cargo.toml,go.mod,pom.xml,Gemfile,composer.json, or equivalent CONTRIBUTING.md,ARCHITECTURE.md,docs/index — if present
Extract
- One-sentence purpose: What does this project do, for whom?
- Domain: What problem space does it operate in?
- Stage: Early build, growth, or mature/stable?
- Key dependencies: Frameworks, databases, external services
If the README is absent or unhelpful, infer purpose from the manifest description field, directory names, and import patterns.
Phase 2 — Shape
Map the physical layout without reading file contents yet.
# Get directory tree (depth 2–3 depending on project size)
find . -type f | head -200
# or
tree -L 3 -I 'node_modules|.git|dist|build|__pycache__|venv|.venv|target'
Categorize top-level directories
| Role | Common names | What to look for |
|---|---|---|
| Source | src/, lib/, app/, pkg/, internal/ |
Production code |
| Tests | test/, tests/, spec/, __tests__/ |
Test suites |
| Config | Root dotfiles, config/, .github/ |
Build/CI/lint config |
| Docs | docs/, doc/, wiki/ |
Documentation |
| Infra | infra/, deploy/, terraform/, k8s/, docker/ |
Deployment |
| Scripts | scripts/, bin/, tools/ |
Automation helpers |
| Generated | dist/, build/, out/, target/ |
Build artifacts (skip) |
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.
- 2d ago First seen · 252 lines · 96 tokens per session scan A 0053fc01fd6b
orient is a skill published in the GitHub repository jcottam/agent-resources (30 stars, last pushed 27d ago), licensed MIT. It adds 96 tokens to every session and 2,184 once invoked, about $0.0005 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
sandbox-next
Use when building or changing Cloudflare Sandbox apps on @cloudflare/sandbox@next (Sandbox SDK 1.0 preview)—code execution, AI runners, interpreters, CI-like jobs, terminals, files, mounts, tunnels, preview URLs, lifecycle, or errors. Not for the default stable package (use sandbox-stable) or for porting stable to…
durable-objects
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases…
80-livekit-agents-majiayu000-claude-skill-registr
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
turnstile-spin
Set up Cloudflare Turnstile end-to-end in a project. Scan the codebase, create the widget via the Cloudflare API, embed it where user requests need bot verification (form submissions, SPA actions, API endpoints, download links, comment or vote submissions, etc.), wire canonical server-side siteverify in the customer's…
dag-factory
Authors Apache Airflow DAGs declaratively from dag-factory YAML configs. Use when building DAGs declaratively from YAML via dag-factory; creating/editing dag-factory templates/YAML configs,reating/editing dag-factory YAML configs, defaults, dynamic tasks, datasets, or callbacks; or validating dag-factory…
deploying-airflow
Deploys Airflow DAGs and projects. Use when deploying Airflow or answering anything about deployment - deploying DAGs/projects, pushing code, setting up CI/CD, deploying to production or deployment strategies for Airflow.