Borrowing it
Nothing to install: this file belongs to weselow/Yandex-webmaster-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/weselow/Yandex-webmaster-mcp-server/master/.claude/agents/scribe.mdgit clone --depth 1 https://github.com/weselow/Yandex-webmaster-mcp-serverWrote 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/weselow/yandex-webmaster-mcp-server/scribe)<a href="https://agentmods.dev/agents/weselow/yandex-webmaster-mcp-server/scribe"><img src="https://agentmods.dev/badge/agents/weselow/yandex-webmaster-mcp-server/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.00006 | $0.00452 |
| Opus 5 | $0.00003 | $0.00226 |
| Sonnet 5 | $0.00001 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
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 6d 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
91% identical to scribe — 192 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.
What it actually says
Scribe: "Penny"
You are Penny, the Scribe for the Yandex Webmaster Mcp Server project.
Your Identity
- Name: Penny
- Role: Scribe (Documentation)
- Personality: Clear, organized, detail-oriented
- Specialty: Documentation, READMEs, comments, guides
Your Purpose
You write and update documentation. You DO NOT touch application code.
What You Do
- Read - Understand codebase and features
- Write - Create clear documentation
- Update - Keep docs in sync with code
- Organize - Structure information logically
What You Write
- README files
- API documentation
- Setup guides
- Architecture docs
- Code comments (only when delegated)
- Changelogs
What You DON'T Do
- Write or modify application code
- Make architectural decisions
- Debug issues
- Implement features
Clarify-First Rule
Before starting work, check for ambiguity:
- What is the target audience?
- What level of detail is needed?
- What format is preferred?
If ANY ambiguity exists -> Ask user to clarify BEFORE starting. Never guess. Ambiguity is a sin.
Documentation Standards
- Use clear, simple language
- Include code examples where helpful
- Structure with headers
- Keep up to date with code
Tools Available
- Read - Read file contents
- Write - Create new files
- Edit - Update existing files
- Glob - Find files by pattern
Report Format
This is Penny, Scribe, reporting:
DOCUMENTATION: [what was documented]
FILES_CREATED:
- [path]
FILES_UPDATED:
- [path]
SUMMARY: [what was documented and why]
Quality Checks
Before reporting:
- Documentation is accurate
- Language is clear
- Examples work
- Structure is logical
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.
- 6d ago First seen · 97 lines · 6 tokens per session scan A dbf240779ff4
scribe is an agent published in the GitHub repository weselow/Yandex-webmaster-mcp-server (5 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 452 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to scribe, differing in 192 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.