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/plipowczan/claude-piv-skeleton/piv-apigit clone --depth 1 https://github.com/plipowczan/claude-piv-skeletonWrote 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/plipowczan/claude-piv-skeleton/piv-api)<a href="https://agentmods.dev/rules/plipowczan/claude-piv-skeleton/piv-api"><img src="https://agentmods.dev/badge/rules/plipowczan/claude-piv-skeleton/piv-api.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.00000 | $0.00217 |
| Opus 5 | $0.00000 | $0.00109 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
piv-api 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 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.
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
API Design Rules
RESTful Principles
- Nouns over verbs:
/usersnot/getUsers - Plural nouns:
/usersnot/user - HTTP verbs: GET (read), POST (create), PUT (update), DELETE (remove)
- Resource hierarchy:
/users/{id}/posts
Response Format
// Success
{ "data": {...}, "meta": {...} }
// Error
{ "error": "ErrorCode", "message": "Human-readable description" }
Best Practices
- Use proper HTTP status codes (200, 201, 400, 404, 500)
- Validate all input
- Version your API (
/v1/users) - Return consistent response structures
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 · 31 lines · 0 tokens per session scan A ade1d5da1572
piv-api is a cursor rule published in the GitHub repository plipowczan/claude-piv-skeleton (4 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 217 tokens. 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.