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/quinnjr/threads-mcp/update-websitegit clone --depth 1 https://github.com/quinnjr/threads-mcpWhat 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.00116 | $0.00116 |
| Opus 5 | $0.00058 | $0.00058 |
| Sonnet 5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
update-website 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 3d 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
After completing any significant feature, update, or change to the project, update the relevant documentation on the GitHub Pages website (docs/ directory) to reflect the changes. This includes:
- Updating the main timeline (index.html) with new feature announcements as thread posts
- Adding new versions to changelog.html with detailed change notes
- Updating any affected documentation pages (API.md, EXAMPLES.md, etc.)
- Ensuring the website accurately represents the current state of the project
Always commit and push website updates along with the code changes.
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.
- 3d ago First seen · 13 lines · 116 tokens per session scan A f705709d3ff4
update-website is a cursor rule published in the GitHub repository quinnjr/threads-mcp (14 stars, last pushed 4mo ago), licensed MIT. It adds 116 tokens to every session, about $0.0006 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
cli-stability
CLI command stability and interface preservation.
remote-pc
Drive a host running agentic-remote-pc over its MCP runner. Use when the user asks to run commands on a remote PC, drive a coding-agent CLI on a host, or validate a local feature/deployment.
dev
This rule is triggered when the user types @dev and activates the Full Stack Developer agent persona.
qa
This rule is triggered when the user types @qa and activates the Test Architect & Quality Advisor agent persona.
ux-expert
This rule is triggered when the user types @ux-expert and activates the UX Expert agent persona.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.