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/ai-agent-filesgit 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/instructions/rshade/finfocus/ai-agent-files)<a href="https://agentmods.dev/instructions/rshade/finfocus/ai-agent-files"><img src="https://agentmods.dev/badge/instructions/rshade/finfocus/ai-agent-files.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 | $0.00417 | $0.00417 |
| Opus 5 | $0.00209 | $0.00209 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
finfocus ai-agent-files.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 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.
What it actually says
AI Agent Instruction Files
This repository contains AI agent instruction files that provide guidance for different AI assistants working with the codebase.
Supported Files:
- CLAUDE.md: Instructions for Claude Code (claude.ai/code)
- GEMINI.md: Instructions for Gemini AI assistants
- AGENTS.md: General agent instructions for various AI tools
Usage Guidelines:
- Read these files when working with AI assistants
- Reference the appropriate file based on the AI tool being used
- Follow the instructions provided in these files
- Keep instructions updated as the codebase evolves
File Purposes:
- CLAUDE.md: Comprehensive development guidelines, build commands, architecture overview, testing requirements
- GEMINI.md: Concise development guidelines, active technologies, workflow restrictions
- AGENTS.md: Repository guidelines, coding standards, project structure, development commands
Maintenance Requirements:
- Update regularly as codebase changes
- Keep version information current (Go versions, dependencies)
- Document new patterns and conventions
- Include new tools and technologies
- Update build/test commands as they change
Integration with Copilot:
- These files are automatically read by GitHub Copilot
- Use them as reference for consistent development practices
- Follow the coding standards and patterns documented
- Reference the build and testing instructions provided
When to Update:
- New dependencies are added
- Build processes change
- Coding standards evolve
- New tools or technologies are introduced
- Project structure changes
- Testing requirements change
Critical Instructions:
- Never commit changes without user approval (CLAUDE.md restriction)
- Always run tests and linting before completion
- Follow Go 1.25.6+ standards and best practices
- Maintain high test coverage (80%+ target)
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 · 58 lines · 417 tokens per session scan A c5f11133117f
finfocus ai-agent-files.instructions.md is an instructions file published in the GitHub repository rshade/finfocus (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 417 tokens to every session, about $0.0021 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).
langchain-aws AGENTS.md
Instructions for langchain-ai/langchain-aws, covering global development guidelines for the langchain monorepo, project architecture and context, langchain-aws structure, key components and langgraph-checkpoint-aws structure.