Borrowing it
Nothing to install: this file belongs to shahlaukik/money-manager-mcp. 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/shahlaukik/money-manager-mcp/main/.agents/skills/testing-money-manager-mcp/SKILL.mdgit clone --depth 1 https://github.com/shahlaukik/money-manager-mcpWrote 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/skills/shahlaukik/money-manager-mcp/testing-money-manager-mcp)<a href="https://agentmods.dev/skills/shahlaukik/money-manager-mcp/testing-money-manager-mcp"><img src="https://agentmods.dev/badge/skills/shahlaukik/money-manager-mcp/testing-money-manager-mcp/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/skills/shahlaukik/money-manager-mcp/testing-money-manager-mcp"><img src="https://agentmods.dev/badge/skills/shahlaukik/money-manager-mcp/testing-money-manager-mcp.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.00079 | $0.02707 |
| Opus 5.5 | $0.00032 | $0.01083 |
| Sonnet 5.5 | $0.00016 | $0.00541 |
| Haiku 4.5 | $0.00008 | $0.00271 |
Grade A, and why
testing-money-manager-mcp 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Money Manager MCP end-to-end
Verify every tool of this MCP server against the live Money Manager "PC
Manager" web server. The server under test is the local build of this repo
(npm run build → dist/), already added to the client as a stdio MCP server
(e.g. money-manager-dev). Confirm the exact server name from the connected
tools before starting (mcp__<server-name>__<tool-name>).
There is no test runner and no CI. This live protocol IS the verification.
Tool coverage checklist (all 18 — the final report must account for each)
| # | Tool | Where exercised |
|---|---|---|
| 1 | init_get_data |
Phase 0 (first call — baseline context) + 1 |
| 2 | transaction_list |
Phase 0/1, error check, id discovery in Phases 4–5 |
| 3 | transaction_create |
Phase 4 |
| 4 | transaction_update |
Phase 4 |
| 5 | transaction_delete |
Phase 4 (bulk), Phase 5 |
| 6 | summary_get_period |
Phase 1 |
| 7 | summary_export_excel |
Phase 2 (both .xls and .xlsx), error check |
| 8 | asset_list |
Phase 0/1, discovery in Phases 3–5, Phase 7 |
| 9 | asset_create |
Phases 3–4 |
| 10 | asset_update |
Phase 3 |
| 11 | asset_delete |
Phases 3 and 5 |
| 12 | card_list |
Phase 0 (drives card-test decision), 1, 6 |
| 13 | card_create |
Phase 6 (consent-gated, default: run) |
| 14 | card_update |
Phase 6 (consent-gated, test card only) |
| 15 | transfer_create |
Phase 5 |
| 16 | transfer_update |
Phase 5 |
| 17 | dashboard_get_overview |
Phase 1 |
| 18 | dashboard_get_asset_chart |
Phase 1 |
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 · 204 lines · 79 tokens per session scan A 9aae0e1dcbb5
testing-money-manager-mcp is a skill published in the GitHub repository shahlaukik/money-manager-mcp (20 stars, last pushed 25d ago), licensed MIT. It adds 79 tokens to every session and 2,707 once invoked, about $0.0003 per session on Opus 5.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-09-15.
Other skills, from other repositories
payram-testnet-testing
Prove a PayRam install works end-to-end on testnet before touching real money — install on testnet, create a payment link, fund a wallet from a faucet, actually pay the link, and confirm the payment reaches FILLED. Covers Base Sepolia / Ethereum Sepolia funding, how a PayRam checkout takes payment, and every way to…
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…