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 markerikson/opencode-config-example --skill project-overviewgit clone --depth 1 https://github.com/markerikson/opencode-config-exampleWrote 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/markerikson/opencode-config-example/project-overview)<a href="https://agentmods.dev/skills/markerikson/opencode-config-example/project-overview"><img src="https://agentmods.dev/badge/skills/markerikson/opencode-config-example/project-overview/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/markerikson/opencode-config-example/project-overview"><img src="https://agentmods.dev/badge/skills/markerikson/opencode-config-example/project-overview.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.00041 | $0.01391 |
| Opus 5.5 | $0.00016 | $0.00556 |
| Sonnet 5.5 | $0.00008 | $0.00278 |
| Haiku 4.5 | $0.00004 | $0.00139 |
Grade A, and why
project-overview 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Overview Skill
Create comprehensive project overview documents that provide strategic context and understanding for major projects or features.
When to Use This Skill
- Starting a major project (multi-week effort)
- Significant architectural changes
- Cross-team initiatives needing shared context
- Prototypes that will inform production work
- Dogfooding/validation projects
Don't use for:
- Small bug fixes
- Single-feature additions
- Routine maintenance work
Document Template
Title and Metadata
# [Project Name]: Project Overview
**Project Name:** [Short identifier]
**Status:** [Planning / In Progress / Complete]
**Timeline:** [Estimated duration]
**Purpose:** [One-sentence summary]
---
Section 1: Understanding the Context
Provide background for someone unfamiliar with the project. Answer:
- What is the system/codebase you're working in?
- What prior work led to this? (prototypes, experiments, decisions)
- What recent progress or decisions have been made?
Length: 3-5 paragraphs
Example:
## Understanding the Context
### What is [System Name]?
[Brief description of the system, its purpose, what it generates/does]
### The [Prototype/Reference Project]
[Describe any reference implementation or prototype that validated the approach]
### Recent Progress
[Key decisions or progress that led to this work]
Section 2: What is This Project?
Define the project scope clearly.
## What is This Project?
### Current State
[Describe what exists today and why it's insufficient]
### Target State
[Describe the desired end state]
### Important Scope Decisions
**In Scope:**
- [What you ARE doing]
**Out of Scope:**
- [What you are NOT doing - be explicit]
Critical: Use blockquotes or callouts for major scope constraints:
> **⚠️ SCOPE:** This focuses exclusively on [X]. We are NOT:
> - [Thing 1]
> - [Thing 2]
Section 3: Why This Work Matters
Explain the value. Don't assume it's obvious.
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 · 261 lines · 41 tokens per session scan A eabb86c3efe2
project-overview is a skill published in the GitHub repository markerikson/opencode-config-example (48 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,391 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…