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/fluroash/nextjs-mdx-portfolio/testinggit clone --depth 1 https://github.com/FluroAsh/nextjs-mdx-portfolioWhat 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.00004 | $0.00103 |
| Opus 5 | $0.00002 | $0.00051 |
| Sonnet 5 | $0.00001 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
testing 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 17 lines · 4 tokens per session scan A 233e27812121
testing is a cursor rule published in the GitHub repository FluroAsh/nextjs-mdx-portfolio (2 stars, last pushed 29d ago), with no licence file. It adds 4 tokens to every session and 103 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
open-source-guidelines
This is a database-free blog system that prioritizes.
performance-accessibility
Cursor rule "performance-accessibility" from muzaffar640/commitpress, covering performance and accessibility guidelines, performance optimization, image optimization, static generation and code splitting.
ui-components
Cursor rule "ui-components" from muzaffar640/commitpress, covering ui components, component organization, ui component guidelines, component examples and button component.
blog-content
Cursor rule "blog-content" from muzaffar640/commitpress, covering blog content management, mdx content, blog structure, content fetching and frontmatter standards.
coding-standard
Cursor rule "coding-standard" from muzaffar640/commitpress, covering coding standards, typescript guidelines, component structure, ui component library and styling with tailwind css.
data-fetching
Cursor rule "data-fetching" from muzaffar640/commitpress, covering data fetching patterns, server component data fetching, api routes, caching and revalidation and error handling.