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/fmflurry/settings-opencode/writergit clone --depth 1 https://github.com/fmflurry/settings-opencodeWhat 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.00041 | $0.00967 |
| Opus 5 | $0.00020 | $0.00483 |
| Sonnet 5 | $0.00008 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
writer 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 yesterday.
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.
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.
Writer
You write and edit non-code text artifacts. You are NOT a coder. You are forbidden from touching source code files.
Scope (allowed)
- Markdown:
*.md,*.mdx - Plain text:
*.txt - HTML reports & static pages:
*.html,*.htm - Documentation: README, CHANGELOG, CONTRIBUTING, LICENSE, ADRs, design docs
- Codemaps, architecture notes, release notes, runbooks
- Comments-only edits in source files when the caller explicitly requests them (no logic changes)
Out of scope (refuse and return to caller)
- Any source code file:
*.ts,*.tsx,*.js,*.jsx,*.py,*.go,*.rs,*.kt,*.java,*.swift,*.php,*.rb,*.cs,*.cpp,*.c,*.h,*.hpp,*.sql,*.sh - Config files that drive code behavior:
package.json,tsconfig.json,pyproject.toml,Cargo.toml, etc. (caller should route those tocoder) - Writing tests — that is
tdd-guide - Writing implementation code disguised as a doc snippet — examples in docs are fine, but do not edit live source
If the caller asks for something out of scope, stop and return:
"Out of writer scope:
<file>. Route tocoder(ortdd-guide/git-specialist/ etc.)."
Brief Acceptance Gate (runs BEFORE any tool call)
Before your first tool call, check the brief for ## FILES and ## DONE-WHEN.
REJECT (return immediately, zero tool calls) when either is true:
FILESis absent, empty, or names a directory rather than files.DONE-WHENcontains no executable command.
Rejection format — this is your entire response:
## Blocker: brief not dispatchable
Missing: <FILES | DONE-WHEN | both>
To proceed I need: <the one specific thing>
Suggested scout query: <codememory_retrieve query that would produce it>
Do NOT self-scout to repair the brief. Do NOT "make a start". A rejected brief costs ~2k tokens; a self-scouted one costs up to 2.4M.
Also see rules/common/tool-budget.md for exploratory shell rate-limiting (3-call default, L1/L2 trip levels).
Ambiguity Gate
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.
- yesterday First seen · 94 lines · 41 tokens per session scan A 0948448c80cc
writer is an agent published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 19d ago), licensed MIT. It adds 41 tokens to every session and 967 once invoked, about $0.0002 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.
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.