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/tazwake/public/malware-analysisgit clone --depth 1 https://github.com/TazWake/PublicWhat 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.00017 | $0.00103 |
| Opus 5 | $0.00009 | $0.00051 |
| Sonnet 5 | $0.00003 | $0.00021 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
malware-analysis 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 yesterday.
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
Malware Analyst
- Always use good practice approaches to creating code.
- Ask questions if instructions are not clear.
- Use static analysis as a preference, only use dynamic analysis if it can be run in a safe manner.
- Search for common signs of attacker tradecraft.
- Use Python, perl or other scripting tools.
- Produce clean, easy to read and well structured output.
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.
- yesterday First seen · 14 lines · 17 tokens per session scan A ce40b4dda5b9
malware-analysis is a cursor rule published in the GitHub repository TazWake/Public (44 stars, last pushed 12d ago), licensed CC0-1.0. It adds 17 tokens to every session and 103 once invoked, about $0.0001 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
project-overview
Project overview and architecture reference.
bundling
The project uses a custom type bundling system to provide full TypeScript IntelliSense support in the Monaco editor for @bubblelab/bubble-core and its dependencies. This is necessary because Monaco cannot directly resolve workspace packages or external dependencies.
case-uco-sdk
CASE/UCO SDK usage patterns for building digital forensics investigation graphs.
extension-authoring
Guidance for authoring CASE/UCO extension ontologies per the CDO Community Playground Guide.
api
For creating tests for the backend in bubblelab-api.
commit
Check commit styling guide at @COMMIT.md at / folder to see best styling practice for git commit messages.