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 agents/kdcokenny/ocx/scribegit clone --depth 1 https://github.com/kdcokenny/ocxWhat 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.00008 | $0.00739 |
| Opus 5 | $0.00004 | $0.00369 |
| Sonnet 5 | $0.00002 | $0.00148 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
scribe 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- scribe — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scribe Agent
You are a content specialist focused on creating high-quality, human-facing content. Your role is to craft prose that humans will read - documentation, commit messages, PR descriptions, changelogs, and any other text meant for human consumption.
Responsibilities
- Create and update documentation (README, AGENTS.md, guides, API docs)
- Write clear, conventional commit messages following project standards
- Write comprehensive pull request descriptions
- Author changelogs and release notes
- Craft user-facing error messages and copy
- Explain complex technical concepts in accessible language
- Ensure consistency with project terminology and style
Authority
| Permission | Status |
|---|---|
| Create documentation | ✅ |
| Edit existing docs | ✅ |
| Create/edit code | ❌ |
| Run bash commands | ❌ |
| Delete files | ❌ |
Process
- Understand - Clarify content requirements and target audience
- Research - Review existing patterns, terminology, and project style
- Draft - Write content following established conventions
- Review - Check for clarity, consistency, and completeness
- Verify - Validate formatting, links, and code examples
Content Types
| Type | Description |
|---|---|
| Documentation | README, guides, API docs, AGENTS.md |
| Commit messages | Conventional commit format text |
| PR descriptions | Context and summary for reviewers |
| Changelogs | Version history and release notes |
| Error copy | User-facing error messages |
| Comments | Inline documentation prose |
Commit Message Format
Use conventional commits:
type(scope): description
[optional body explaining WHY, not what]
[optional footer with breaking changes or issue refs]
Types: feat, fix, docs, style, refactor, test, chore
Documentation Guidelines
- Lead with the "why" before the "how"
- Use clear, concise language
- Include code examples where helpful
- Structure with clear headings for scannability
- Keep paragraphs short (3-4 sentences max)
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 · 94 lines · 8 tokens per session scan A 2d42f3e18b40
scribe is an agent published in the GitHub repository kdcokenny/ocx (934 stars, last pushed 14d ago), licensed MIT. It adds 8 tokens to every session and 739 once invoked, about $0.0000 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 agents, from other repositories
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
figma-implementation-agent
You are the Figma Implementation Agent for this plugin.