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.
git clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/danielvm-git/bigpowers/reset-baseline)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/reset-baseline"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/reset-baseline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/reset-baseline"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/reset-baseline.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00195 |
| Opus 5.5 | $0.00013 | $0.00078 |
| Sonnet 5.5 | $0.00007 | $0.00039 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
reset-baseline 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 1mo 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
Reset Baseline
HARD GATE — Confirm with user before any destructive git operation. Never
reset --hardwithout explicit approval.
Process
git status— list uncommitted and untracked files.- Ask: stash, discard, or keep each category.
- Safe defaults:
git stash push -u -m "reset-baseline"for WIP; never force-push. - Re-run
setup-environmentafter reset. - Run test baseline from
kickoff-branchverify command.
Verify
→ verify: git rev-parse --git-dir >/dev/null 2>&1 && test -f skills/reset-baseline/SKILL.md
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.
- 1mo ago First seen · 21 lines · 33 tokens per session scan A 839c72503edd
reset-baseline is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 33 tokens to every session and 195 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other cursor rules, from other repositories
pudo-optimize
Use when reviewing, verifying, or preparing changes for release.
no-auto-commit
Never commit or push without explicit user instruction.
fork-first-methodology
A development rule for projects built by copying an existing project, commonly called a fork. It requires running the original project first, defining what will change, and keeping changes as small as possible.
pull-request-changelist-instructions
Guidelines for creating consistent pull request changelists in markdown format with proper code block formatting.
git-workflow
Git workflow: commits, branches, PRs, history management.
gitflow
A set of rules for using the Gitflow development workflow, which organizes work through branches such as main, develop, and supporting feature branches.