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 skills/dinerojs/dinero.js/commitnpx skills add dinerojs/dinero.js --skill commitgit clone --depth 1 https://github.com/dinerojs/dinero.jsWhat 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.00021 | $0.00704 |
| Opus 5 | $0.00010 | $0.00352 |
| Sonnet 5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
commit 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow
Step 1: Analyze Changes
Run these commands to understand what's being committed:
git status
git diff --staged
git diff
If there are no staged changes, ask the user what to stage or suggest relevant files based on unstaged changes.
Step 2: Find Related Linear Issues
Use the Linear MCP tools to search for related issues:
-
List open issues in the Dinero.js project:
mcp__linear-server__list_issues with: - project: "Dinero.js v2.0.0 Stable Release" - state: "backlog" or "in_progress" or "todo" -
Search by keywords from the changes (function names, file paths, feature areas)
-
Present matching issues to the user in a table:
ID Title Status SAR-110 Restructure packages... Backlog
Step 3: User Selection
Ask the user using AskUserQuestion:
- Which issue(s) does this commit relate to?
- Does this commit complete the issue (Fixes) or is it partial progress (Part of)?
Options:
- Select from found issues
- Enter a different issue ID
- No Linear issue (skip linking)
Step 4: Create Commit
Generate a commit message following Conventional Commits format:
type(scope): subject
Description of changes.
[Fixes|Part of] SAR-XXX
Co-Authored-By: Claude Opus 4.5 <[email protected]>
Types: feat, fix, docs, refactor, test, chore, style, perf Scopes: core, currencies, calculator-number, calculator-bigint, dinero.js, examples, docs, build, ci
Step 5: Execute
- Stage files if needed (prefer specific files over
git add -A) - Create the commit using a HEREDOC for proper formatting
- Run
git statusto confirm success - If the commit completes an issue, offer to update it in Linear using
mcp__linear-server__update_issue
Examples
Completing an issue
git commit -m "$(cat <<'EOF'
feat(core): add subpath exports for currencies
Implemented exports field in package.json with proper TypeScript support
for all subpath entries.
Fixes SAR-111
Co-Authored-By: Claude Opus 4.5 <[email protected]>
EOF
)"
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 · 113 lines · 21 tokens per session scan A 2af91cc9c090
commit is a skill published in the GitHub repository dinerojs/dinero.js (6,793 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 704 once invoked, about $0.0001 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-30.
Other skills, from other repositories
implementing-providers
Use when adding a new exchange rate data provider, implementing a provider from a GitHub issue, when the user mentions a new central bank or data source, or when working on any issue labeled "provider". Also use when asked to backfill, fix, or update an existing provider.
evaluating-pegs
Use when adding, evaluating, or removing an entry in db/seeds/pegs/, when the user mentions a pegged or fixed currency, or when an issue suggests we should "pin" or "lock" a currency to another. Also use when deciding whether to filter or override provider rates based on an assumed peg.
wise-api
Use when querying Wise for exchange rates (real-time or historical), validating Frankfurter rates against Wise mid-market, debugging rate discrepancies, or when the user mentions Wise, sanity check, or rate comparison.
electron-node-upgrade
Guide for performing Node.js version upgrades in the Electron project. Use when working on the roller/node/main branch to fix patch conflicts during e sync --3. Covers the patch application workflow, conflict resolution, analyzing upstream Node.js changes, building, running the Node.js test suite, and proper commit…
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
Shade dropdown surface contract
DropdownMenu, Select, and Popover share one visual recipe (bg-surface-elevated-2 + border-border/60 dark:border-border/30 + shadow-md). Change them together. Trigger when editing any of those three Shade files.