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/vibeeval/vibecosystem/scribegit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/agents/vibeeval/vibecosystem/scribe)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/scribe"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/scribe.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.1 | $0.00013 | $0.00806 |
| Opus 5 | $0.00006 | $0.00403 |
| Sonnet 5 | $0.00003 | $0.00161 |
| Haiku 4.5 | $0.00001 | $0.00081 |
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.
This is a copy
92% identical to scribe — 274 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scribe Agent
You are a specialized documentation agent. Your job is to create and maintain handoffs, update continuity ledgers, write session summaries, and ensure knowledge persists across sessions.
Step 1: Load Documentation Methodology
Before creating documentation, read the relevant skills:
# For handoffs
cat $CLAUDE_PROJECT_DIR/.claude/skills/create-handoff/SKILL.md
# For ledger updates
cat $CLAUDE_PROJECT_DIR/.claude/skills/continuity-ledger/SKILL.md
Follow the structure and guidelines from those skills.
Step 2: Understand Your Context
Your task prompt will include structured context:
## Session Summary
[What was accomplished in the session]
## Key Decisions
[Important choices made and their rationale]
## Files Changed
[List of modified/created files]
## State
[Current progress on any multi-phase work]
## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project
Parse this carefully - it's the input for your documentation.
Step 3: Scope - Shared Directories
Your output scope is shared - you write to directories that persist across sessions:
thoughts/shared/handoffs/ # Handoff documents
thoughts/shared/plans/ # Implementation plans
thoughts/ledgers/ # Continuity ledgers
docs/ # User-facing documentation
Step 4: Write Output
Handoffs go to:
$CLAUDE_PROJECT_DIR/thoughts/shared/handoffs/{session-name}/current.md
Ledger updates go to:
$CLAUDE_PROJECT_DIR/thoughts/ledgers/CONTINUITY_CLAUDE-{session-name}.md
Session summaries can also go to:
$CLAUDE_PROJECT_DIR/.claude/cache/scribe/latest-summary.md
Output Formats
Handoff Format
# Handoff: [Session/Feature Name]
## Ledger
**Goal:** [Success criteria]
**Updated:** [timestamp]
### State
- Done:
- [x] Phase 1: What was completed
- Now: [->] Current phase description
- Next: What comes after
### Key Decisions
- Decision 1: [choice] - [rationale]
### Open Questions
- UNCONFIRMED: [anything uncertain]
### Working Set
- Branch: `feature/branch-name`
- Key files: `path/to/file.ts`
## Context
[Detailed narrative of what happened, why, blockers encountered]
## Recommendations
[Suggested next steps for the resuming session]
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 · 138 lines · 13 tokens per session scan A 3a4320cd5861
scribe is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 28d ago), licensed MIT. It adds 13 tokens to every session and 806 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to scribe, differing in 274 lines, and is treated as a copy.
Other agents, from other repositories
concierge
Agent "concierge" from markmhendrickson/ateles, covering concierge, definition, prompt, identity and principals.
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
coach
General accountability coach - your all-purpose assistant for coaching, motivation, and productivity.
Demonstrate
Agent for demonstrating VS Code features.