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 doordash-oss/agentic-orchestrator --skill knowledge-readergit clone --depth 1 https://github.com/doordash-oss/agentic-orchestratorWrote 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/doordash-oss/agentic-orchestrator/knowledge-reader)<a href="https://agentmods.dev/skills/doordash-oss/agentic-orchestrator/knowledge-reader"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/knowledge-reader/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/doordash-oss/agentic-orchestrator/knowledge-reader"><img src="https://agentmods.dev/badge/skills/doordash-oss/agentic-orchestrator/knowledge-reader.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.00026 | $0.00662 |
| Opus 5.5 | $0.00010 | $0.00265 |
| Sonnet 5.5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
knowledge-reader 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 1mo 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Base Reader
You have access to a pre-built Knowledge Base (KB) for the target repository. The KB index path and KB directory are listed in the Pre-flight section of your prompt — read the KB index first to see what categories are available.
The KB is a structured graph of markdown documents organized into categories. Each category has an index file and detailed leaf files. Start by reading the KB index, then use the KB directory path to read specific leaf files relevant to your task.
When to Read KB Leaf Files
Consult the KB before you:
| Situation | Read from these KB categories |
|---|---|
| Write or modify code | conventions/ — read the index, then leaf files for error handling, naming, code style |
| Write or modify tests | verification/ + conventions/ — test patterns, test infrastructure, testing conventions |
| Make architectural decisions | architecture/ — components, data flow, key abstractions |
| Use or extend APIs | api-surface/ — services, client libraries, config schemas |
| Add dependencies | dependencies/ — approved libraries, version constraints |
| Set up verification steps | verification/ — test suites, CI pipeline, verification order |
How to Navigate
- Read the KB index from the path listed in Pre-flight — it shows the category map, build commands, key architecture decisions, and important file paths
- Identify which categories are relevant to your current task using the table above
- Read the category's
index.mdfirst (e.g.,<KB Directory>/conventions/index.md) to discover the actual leaf filenames — these vary per repo - Read the relevant leaf files based on what the category index lists
- Only read what you need — typically 2-4 leaf files per task
Category Overview
| Category | What it covers |
|---|---|
architecture/ |
Component maps, data flow patterns, dependency injection modules, key abstractions, concurrency and persistence models |
conventions/ |
Error handling patterns (including error grading), naming conventions, testing patterns, code style, logging and context propagation |
api-surface/ |
gRPC services, CLI tools, client library API, configuration schemas, environment variables, Kafka event contracts |
dependencies/ |
Go library inventory, build tools (Task, Bazel, etc.), runtime services (Cassandra, CRDB, Kafka), version constraints |
verification/ |
Unit test patterns, integration test infrastructure, CI pipeline, linting rules, recommended verification order |
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.
- 1mo ago First seen · 49 lines · 26 tokens per session scan A a6746ae0a9e8
knowledge-reader is a skill published in the GitHub repository doordash-oss/agentic-orchestrator (115 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 662 once invoked, about $0.0001 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-30.
Other skills, from other repositories
plan-pm
Principal PM skill — the autonomous PRD writer. Consumes a graded, fleshed-out row from the INTAKE.md backlog (idea, goal, type, grade) and drafts the full PRD solo — feature/acceptance table, edge cases, error handling — saved to features/planned/prd-[n]-[feature-slug]/. The requirements interview lives in /intake…
pre-merge
The quality gate. Takes a feature branch from "eng says done" to "checked, fixed and ready for /merge". Runs the project's preflight-resolved pipeline from devkit/policy.json components[]: sync → parallel correctness + security waves → coverage → regression tail → security/migration → PRD-consistency → verdict. A…
intake
The planning front-door. Captures feature ideas and bugs as graded rows in the root INTAKE.md ledger. Use it when the user says "log an idea", "capture a bug", "add to the backlog", "note this down", "track this feature", or invokes /intake. Opens with one prompt ("What are you trying to build?"), infers the rest from…
msg
Root menu for msg skills, plus harness modes. Bare /msg says the next step for each PRD in progress and offers to run it — use it when the user says "what's next", "where am I", "what should I run now". --init is the project setup — use it when the user says "initialise project", "bootstrap repo", "set up the…
plan-em
Engineering Manager skill. Reads an approved PRD, runs pre-flight checks against AHA.md, GLOSSARY.md and ARCHITECTURE.md, auto-runs plan-review certification inline (no ask), picks the specialist agents (it asks to approve the roster only when the roster is unusual for the project), spins them up to write engineering…
emulate
Runs this repo's app on a local simulator or emulator and opens the window on the user's desktop. Use it when the user says "run the app", "open the simulator", "launch the emulator", "boot the iOS sim", "start Expo", "see it running", "show me the app", or invokes /emulate. Takes the branch the user is standing on…