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/delorenj/ssbnk/scribegit clone --depth 1 https://github.com/delorenj/ssbnkWhat 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.
This is a copy
100% identical to scribe — 0 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 — 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 delorenj/ssbnk (2 stars, last pushed 4d 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. It is 100% identical to scribe, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
db2-dba
DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
prompt_engineer
Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example…
code_reviewer
Code review specialist for identifying bugs, security vulnerabilities, and code quality issues. Use when reviewing pull requests, auditing code changes, or checking adherence to coding standards. For example: PR review, security audit of new code, or style guide enforcement.
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.