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/rshade/finfocus/finfocus-technical-writergit clone --depth 1 https://github.com/rshade/finfocusWhat 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.00282 | $0.01217 |
| Opus 5 | $0.00141 | $0.00609 |
| Sonnet 5 | $0.00056 | $0.00243 |
| Haiku 4.5 | $0.00028 | $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 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.
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.
- 3d 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 (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 282 tokens to every session and 1,217 once invoked, about $0.0014 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-31.
Other agents, from other repositories
plan-alternative
Fresh-context alternative designer. Given the GOAL a plan is trying to achieve, ignores the proposed plan and designs the simplest thing that meets the goal from scratch, then judges whether that alternative materially dominates the proposal. Does not attack the plan (that is plan-adversary's job) and does not write…
analyzer
:::info[Source] This page is generated from skills/skill-creator/agents/analyzer.md. Edit the source, not this page. ::.
iac-recon
EKS Infrastructure-as-Code reconnaissance subagent.
ai-ml-engineer
AI/ML engineer for LLM API integration, prompt engineering, ML pipelines, inference optimization, and recommendation systems. Do NOT use for general CRUD work, UI design, or non-AI infrastructure.
claude-aws-architect-implementation-agent
USE FOR Translating an accepted design.md into IaC, IAM policies, cost ROM, observability, and acceptance criteria. Authoring per-component contract sections covering IaC, Cost, Security, Acceptance, Observability. Drafting tasks.md from the merged design under the bundled implementation specialist contract. DO NOT…
inference-gateway-operator
Agent "inference-gateway-operator" from aws-samples/sample-oh-my-aidlcops, covering 역할 (role), core capabilities, decision tree, common commands and kgateway 설치.