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/ya5huk/findash/claude-mdgit clone --depth 1 https://github.com/ya5huk/findashWrote 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/ya5huk/findash/claude-md)<a href="https://agentmods.dev/instructions/ya5huk/findash/claude-md"><img src="https://agentmods.dev/badge/instructions/ya5huk/findash/claude-md.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.1 | $0.03120 | $0.03120 |
| Opus 5 | $0.01560 | $0.01560 |
| Sonnet 5 | $0.00624 | $0.00624 |
| Haiku 4.5 | $0.00312 | $0.00312 |
Grade B, and why
findash CLAUDE.md scanned grade B with 1 finding 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- `qpdf` is required to unlock payslip PDFs. Install: `sudo apt install -y qpdf`. This is a copy
89% identical to findash AGENTS.md — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
findash
Personal finance system, packaged as a Claude Code plugin (findash). Drive vault + configured feeds → SQLite → local React dashboard. sync-finance-data is the complete update: it runs fetch-bank-data, attempts fetch-investments, gathers Drive drops, ingests and reconciles everything, refreshes cached market data, and performs the gated backup. ./run_dashboard.sh runs the localhost React dashboard; its server appends stock/FX observations every 30 minutes. setup handles onboarding and findash-doctor audits the install. External failures become ⚠️ warnings unless local migration/ingestion cannot continue.
Skills are namespaced by the plugin, so they're invoked as /findash:<skill>. Load the plugin by running Claude Code from the repo root with claude --plugin-dir ..
First principles
These shape every decision in this project. Re-read them when you're about to write code.
-
Public-project hygiene. This repository is public. Keep committed code, docs, examples, and prompts generalized so they work for any user. Never include a real user's account numbers, balances, transaction amounts, counterparties, credentials, tokens, Drive IDs, personal identifiers, or local secret values. Provider names are fine when documenting supported integrations; user-specific financial details are not. Never print, paste, upload, or otherwise share secrets from
.secrets/, local databases, downloaded statements, or generated dashboards. -
Judgment over scripts. Claude's reasoning is the asset, not a parser script. Don't write categorization rules, don't pattern-match filenames mechanically, don't hard-code "if counterparty contains X then category is Y". The example: a large outflow to a brokerage you own is not an expense — it's a transfer. Only Claude can see that, because Claude reads both the bank statement and the brokerage's deposit confirmation in the same session. Scripts can't.
Mechanical work (parsing XLSX bytes, executing SQL, decrypting a PDF with a known password, decoding a connector download into staging) is fine as a script. Interpretation of what the data means is always done by Claude.
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.
- 6d ago First seen · 129 lines · 3,120 tokens per session scan B da3187243015
findash CLAUDE.md is an instructions file published in the GitHub repository ya5huk/findash (19 stars, last pushed 13d ago), licensed MIT. It adds 3,120 tokens to every session, about $0.0156 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 89% identical to findash AGENTS.md, differing in 32 lines, and is treated as a copy.
Other instructions, from other repositories
stockbit-mcp CLAUDE.md
Claude Code instructions for INo-xious/stockbit-mcp, covering claude.md, what this is, commands, the map and three invariants. do not break them; each has a test.
bd-income-tax-skills CLAUDE.md
Instructions for arifulislamat/bd-income-tax-skills: This project's guidance for Claude Code (and any AI agent) lives in AGENTS.md — read it first.
wealth-forge-ai CLAUDE.md
Claude Code instructions for vikisingh23/wealth-forge-ai, covering wealthforge ai: claude instructions, persona, user profile, global mandates and agent specialization mapping.
wealth-forge-ai GEMINI.md
Gemini CLI instructions for vikisingh23/wealth-forge-ai, covering wealthforge ai, agent instructions, financial rules & standards and configuration.
Copilot-Skills kraken-analyst.instructions.md
Instructions for TheSethRose/Copilot-Skills, covering kraken analyst instructions, core capabilities, public api features (no authentication required), private api features (requires api keys) and default behaviors.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).