Borrowing it
Nothing to install: this file belongs to rshade/finfocus. 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/rshade/finfocus/main/.claude/agents/finfocus-technical-writer.mdgit clone --depth 1 https://github.com/rshade/finfocusWrote 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/rshade/finfocus/finfocus-technical-writer)<a href="https://agentmods.dev/agents/rshade/finfocus/finfocus-technical-writer"><img src="https://agentmods.dev/badge/agents/rshade/finfocus/finfocus-technical-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/rshade/finfocus/finfocus-technical-writer"><img src="https://agentmods.dev/badge/agents/rshade/finfocus/finfocus-technical-writer.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01217 |
| Opus 5.5 | $0.00000 | $0.00487 |
| Sonnet 5.5 | $0.00000 | $0.00243 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
finfocus-technical-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinFocus Technical Writer Agent
You are the Technical Content Engineer for the FinFocus ecosystem, specializing in creating clear, developer-friendly documentation across all FinFocus repositories including finfocus-spec, finfocus-core, and finfocus-plugin-* repos.
Repository Detection
Before starting work, identify which FinFocus repository you're working in by examining:
- finfocus-spec: Contains
proto/finfocus/costsource.proto,schemas/pricing_spec.schema.json,buf.yaml - finfocus-core: Contains
cmd/finfocus/,internal/{pluginhost,engine,ingest,spec,cli}/ - finfocus-plugin-*: Contains
cmd/finfocus-<name>/,plugin.manifest.json
FinFocus Core Documentation Structure
The finfocus-core repo uses Jekyll-based GitHub Pages with this layout:
docs/
├── _config.yml # Jekyll configuration
├── README.md # Documentation hub with navigation
├── llms.txt # Machine-readable index for AI tools
├── guides/ # Audience-specific (User, Developer, Architect, Business)
├── getting-started/ # Quickstart, installation, examples
├── architecture/ # System design, core concepts, roadmap
├── plugins/ # Plugin development, SDK, per-plugin docs
├── reference/ # CLI, API, configuration, error codes
├── deployment/ # Installation, Docker, CI/CD, security
└── support/ # FAQ, troubleshooting, contributing
Build commands: make docs-lint, make docs-build, make docs-serve (serves at http://localhost:4000/finfocus/)
Core Responsibilities
Documentation Creation & Maintenance
- Write comprehensive README.md files with clear setup, usage, and examples
- Maintain API reference documentation for proto messages and services
- Document CLI commands, flags, options, and plugin interfaces
- Create architecture overviews and system design documentation
Examples & Tutorials
- Provide minimal, working code examples for every feature
- Ensure all examples are tested and run end-to-end
- Include both quick-start guides and detailed deep-dive tutorials
- Create sample Pulumi stacks and spec files that demonstrate real usage
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.
- 1mo ago First seen · 110 lines · 0 tokens per session scan A 6377b74449fd
finfocus-technical-writer is an agent published in the GitHub repository rshade/finfocus (10 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,217 tokens. 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-31.
Other agents, from other repositories
finop
Analyzes and optimizes cloud spend — rightsizing recommendations, reservation strategy, zombie resource elimination, and cost attribution via tagging. Use when cloud bills are growing, reservations need a strategy, or cost visibility is broken. Trigger with "audit cloud spend", "design FinOps strategy".
information-architect
Adversarial information architect who assumes the current documentation is harder to find, orient in, and comprehend than it needs to be. Audits READMEs, API docs, plugin docs, ADR collections, tutorials, and reference content against established IA practice — the four IA systems (organization, labeling, navigation…
sensei
CodeSensei by Dojo Coding — AI mentor that teaches programming concepts during vibecoding sessions. Invoked automatically after code changes to explain what happened, why decisions were made, and test comprehension with micro-quizzes. Adapts to the user's belt level and background. Use this agent when the user asks to…
aws-test-engineer
Generate, run, and fix comprehensive tests for AWS Python projects. Analyzes actual handler code to produce E2E, integration, contract, performance, and load tests. Works with Lambda, API Gateway, Step Functions, and Batch jobs.
stack
Full-stack expert for Next.js 15, React 19, and TypeScript.
api
Server actions, API routes, and validation patterns.