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 instructions/rshade/finfocus/specsgit 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.00187 | $0.00187 |
| Opus 5 | $0.00093 | $0.00093 |
| Sonnet 5 | $0.00037 | $0.00037 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
finfocus specs.instructions.md 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 2d 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.
What it actually says
Specs Directory Instructions
This directory contains specification files and feature plans that are not part of the main codebase. These files are primarily for project management and planning purposes.
Guidelines for this directory:
- Do not modify existing spec files unless explicitly instructed
- Do not add new spec files without approval
- Do not reference spec files in code or documentation
- Do not commit changes to spec files unless they are part of a planned feature implementation
Purpose:
- Feature planning and requirements gathering
- Cross-repository coordination
- Project milestone tracking
- Historical record of feature decisions
When working with specs:
- Read-only access for understanding project context
- Use information from specs to inform code decisions
- Do not treat specs as authoritative documentation
- Specs may contain outdated or superseded information
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.
- 2d ago First seen · 30 lines · 187 tokens per session scan A 83f030ee0d6e
finfocus specs.instructions.md is an instructions file published in the GitHub repository rshade/finfocus (5 stars, last pushed 16d ago), licensed Apache-2.0. It adds 187 tokens to every session, about $0.0009 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 instructions, from other repositories
costory-finops-mcp-skills AGENTS.md
AGENTS.md instructions for costory-io/costory-finops-mcp-skills, covering agents.md — conventions for ai coding agents in this repo, layout, skill id mapping (costory mcp), when changing a skill and when adding a new skill.
ai-pricing-hub-mcp CLAUDE.md
Claude Code instructions for OptimNow/ai-pricing-hub-mcp, covering claude.md - ai pricing hub mcp app, what this project does, architecture, data sources and the fallback chain and project structure.
ai-pricing-hub-mcp AGENTS.md
AGENTS.md instructions for OptimNow/ai-pricing-hub-mcp: Before writing code, first explore the project structure, then invoke the chatgpt-app-builder skill for documentation.
insideout-power AGENTS.md
Instructions for luthersystems/insideout-power, covering insideout — riley infrastructure agent, what riley can do for you, how to invoke riley, via remote mcp (preferred — use this first) and via agent skills.
cloud-mcp-server CLAUDE.md
Claude Code instructions for alexei-led/cloud-mcp-server, covering aws mcp server development guide, build & test commands, architecture, server (server.py) and sandbox (sandbox.py).
devopness AGENTS.md
Instructions for devopness/devopness, covering agents, core flow, shared constraints, monorepo structure and git workflow.