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/aetosdios27/scribe/stylesnpx skills add aetosdios27/scribe --skill stylesgit clone --depth 1 https://github.com/aetosdios27/scribeWhat 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.00044 | $0.03133 |
| Opus 5 | $0.00022 | $0.01566 |
| Sonnet 5 | $0.00009 | $0.00627 |
| Haiku 4.5 | $0.00004 | $0.00313 |
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 3d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrating Scribe
Principle
Use Scribe as publishing infrastructure inside the website the user already owns. Preserve its routing, deployment, content files, fonts, colors, spacing, and identity.
The host owns visual design. Scribe owns publishing structure and behavior.
When a broad request says to install Scribe or make a blog better, the default result is the existing host design with stronger publishing mechanics. Proceed with that preservation contract; do not stop to ask how extensively to redesign the site. Ask only when the repository contains genuinely conflicting visual directions or the requested change would alter product identity.
Prefer ordinary Markdown and semantic HTML. Use Scribe-specific components only when richer semantics or metadata are genuinely required.
Treat unexpected integration workarounds as possible Scribe defects. Do not silently patch around them in the host application.
Scribe is not a CMS, hosted platform, website builder, rich-text editor, proprietary format, collaboration system, or replacement for React, Next.js, HTML, or MDX.
Scribe 0.1.0-beta is a public beta. Package versions may use prerelease SemVer identifiers while the API is still evolving.
Inspect before changing
- Read the host repository instructions.
- Identify React, Next.js or Vite, MDX versions, package manager, component-map location, global stylesheet entry, theme mechanism, and production build command.
- Inspect the host’s fonts and CSS tokens. Reuse them; do not impose a Scribe font or redesign the site.
- Find one representative article containing headings, code, tables, and images.
- Confirm installed Scribe packages and keep their prerelease versions aligned.
Expected packages are @scribe-sdk/react, @scribe-sdk/styles, @scribe-sdk/mdx, and development-only @scribe-sdk/cli. Read the installed Scribe README and SKILL.md before integrating. Depending on the installed package, these are available under paths such as node_modules/@scribe-sdk/react/README.md and node_modules/@scribe-sdk/react/SKILL.md. Use the packaged copies rather than relying on remembered APIs.
What ships with it
8 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.
- 3d ago First seen · 233 lines · 44 tokens per session scan A 569ec77ff206
scribe is a skill published in the GitHub repository aetosdios27/scribe (11 stars, last pushed 10d ago), licensed Apache-2.0. It adds 44 tokens to every session and 3,133 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…