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 rules/janekbaraniewski/openusage/add-new-providergit clone --depth 1 https://github.com/janekbaraniewski/openusageWrote 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/rules/janekbaraniewski/openusage/add-new-provider)<a href="https://agentmods.dev/rules/janekbaraniewski/openusage/add-new-provider"><img src="https://agentmods.dev/badge/rules/janekbaraniewski/openusage/add-new-provider.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.00034 | $0.00191 |
| Opus 5 | $0.00017 | $0.00096 |
| Sonnet 5 | $0.00007 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
add-new-provider 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 5d 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
@docs/skills/add-new-provider.md contains the full skill specification. Read and follow it completely.
The user's request is to add a new provider. The provider name may be part of their message.
Follow all phases in order:
- Phase 0: Quiz the user for required information
- Phase 1: Research the provider's API
- Phase 2: Create the provider package
- Phase 3: Configure the dashboard widget
- Phase 4: Register the provider and add auto-detection
- Phase 5: Write tests
- Phase 6: Verify with build + test + vet
Do NOT skip the quiz phase. Do NOT proceed without all answers.
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.
- 5d ago First seen · 21 lines · 34 tokens per session scan A 86578cadcae0
add-new-provider is a cursor rule published in the GitHub repository janekbaraniewski/openusage (186 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 191 once invoked, about $0.0002 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.