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/brendadeeznuts1111/telegram-affiliate/package-metadatagit clone --depth 1 https://github.com/brendadeeznuts1111/telegram-affiliateWrote 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/brendadeeznuts1111/telegram-affiliate/package-metadata)<a href="https://agentmods.dev/rules/brendadeeznuts1111/telegram-affiliate/package-metadata"><img src="https://agentmods.dev/badge/rules/brendadeeznuts1111/telegram-affiliate/package-metadata.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.03244 | $0.03244 |
| Opus 5 | $0.01622 | $0.01622 |
| Sonnet 5 | $0.00649 | $0.00649 |
| Haiku 4.5 | $0.00324 | $0.00324 |
Grade C, and why
package-metadata scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"cleanup": "rm -rf *" // Dangerous! Be specific 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.
- 4d ago First seen · 519 lines · 3,244 tokens per session scan C 0948c4b97b42
package-metadata is a cursor rule published in the GitHub repository brendadeeznuts1111/telegram-affiliate (2 stars, last pushed 11d ago), with no licence file. It adds 3,244 tokens to every session, about $0.0162 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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
docs
All documentation files use MDX format with a specific structure.
workers-patterns
Skim this on every task that touches workers, env, routes, or bindings.
git-workflow
Cloud Agents MUST run git add, git commit, and git push before ending their response when they have made code changes. Do not end your turn without pushing. ALWAYS use Pull Requests instead of pushing directly to main.
typescript-imports
Golden rule: import each symbol from the module that defines it. A package index.ts may barrel only its own ./ modules — never another package.
new-env-var-checklist
Checklist when adding any new env secret/variable — Turbo globalEnv, GitHub sync, workflow maps, Alchemy bindings. Prevents "secret synced but worker never gets it".
project-init
When the user has not yet personalized a copy of this monorepo, help them before building features.