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/goondocks-co/open-agent-kit/oaknpx skills add goondocks-co/open-agent-kit --skill oakgit clone --depth 1 https://github.com/goondocks-co/open-agent-kitWrote 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/goondocks-co/open-agent-kit/oak)<a href="https://agentmods.dev/skills/goondocks-co/open-agent-kit/oak"><img src="https://agentmods.dev/badge/skills/goondocks-co/open-agent-kit/oak.svg" alt="Measured on agentmods" 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 | $0.00167 | $0.03403 |
| Opus 5 | $0.00084 | $0.01702 |
| Sonnet 5 | $0.00033 | $0.00681 |
| Haiku 4.5 | $0.00017 | $0.00340 |
Grade A, and why
oak 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 4d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OAK
Prefer MCP tools (oak_search, oak_context, oak_remember, oak_resolve_memory) over CLI when available. Fall back to CLI or direct SQL for queries not covered by MCP tools. If .oak/ci/activities.db does not exist, inform the user to run oak-dev team start first.
Quick Start
MCP tools (preferred when available)
# Search knowledge — memories, plans, and sessions (default)
oak_search(query="authentication refactor decision")
# Narrow by category
oak_search(query="form validation logic", search_type="code")
oak_search(query="backup directory decision", search_type="memory")
oak_search(query="migration plan", search_type="plans")
# Impact analysis — get context for a specific file
oak_context(task="impact of changes to executor", files=["src/features/agent_runtime/executor.py"])
# Store an observation
oak_remember(observation="The backup dir uses a 3-tier priority", memory_type="decision")
# Mark a resolved gotcha
oak_resolve_memory(id="<uuid from oak_search>")
CLI fallback
# Semantic search
oak-dev ci search "retry with exponential backoff" --type code
# Browse memories by type
oak-dev ci memories --type decision
# Get impact context for a specific file
oak-dev ci context "impact of changes" -f src/services/auth.py
Direct SQL (for aggregations, history, custom queries)
# Recent sessions
sqlite3 -readonly -header -column .oak/ci/activities.db \
"SELECT id, agent, title, status, datetime(created_at_epoch, 'unixepoch', 'localtime') as started FROM sessions ORDER BY created_at_epoch DESC LIMIT 5;"
# Query anything
sqlite3 -readonly -header -column .oak/ci/activities.db "SELECT count(*) FROM sessions;"
Commands Reference
CLI commands
| Command | Purpose |
|---|---|
oak-dev ci search "query" --type code |
Semantic vector search for code |
oak-dev ci search "query" --type memory |
Semantic search for memories |
oak-dev ci search "query" -n 20 |
Broader search with more results |
oak-dev ci context "task" -f <file> |
Get context for current work |
oak-dev ci remember "observation" |
Store a memory (NOT via SQL) |
oak-dev ci memories --type gotcha |
Browse memories by type |
oak-dev ci memories --status active |
Browse memories by lifecycle status |
oak-dev ci resolve <id> |
Mark observation as resolved |
oak-dev ci resolve --session <id> |
Bulk-resolve all observations from a session |
oak-dev ci sessions |
List session summaries |
oak-dev team status |
Check daemon status |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 328 lines · 167 tokens per session scan A 06b89b04918e
oak is a skill published in the GitHub repository goondocks-co/open-agent-kit (10 stars, last pushed 1mo ago), licensed MIT. It adds 167 tokens to every session and 3,403 once invoked, about $0.0008 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-31.
Other skills, from other repositories
tiered-memory
Three-tier agent memory model (hot/cold/wiki) for context reduction per spawn.
godot-optimization
Use when optimizing Godot games — profiler, draw calls, physics tuning, memory management, and common bottlenecks.
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
map-debug
Structured MAP debugging via task-decomposer, actor, and monitor agents. Use when reproducing a bug, isolating a regression, or diagnosing an error with specialized agents — including failing or flaky tests (pytest AssertionError), crashes and segmentation faults, memory-corruption or memory errors in native/C…