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/Project-VIC-International/Agentic-AI-Development-CourseWrote 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/project-vic-international/agentic-ai-development-course/auto-research)<a href="https://agentmods.dev/rules/project-vic-international/agentic-ai-development-course/auto-research"><img src="https://agentmods.dev/badge/rules/project-vic-international/agentic-ai-development-course/auto-research.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.1 | $0.01682 | $0.01682 |
| Opus 5 | $0.00841 | $0.00841 |
| Sonnet 5 | $0.00336 | $0.00336 |
| Haiku 4.5 | $0.00168 | $0.00168 |
Grade A, and why
auto-research 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Research: Experiment-Driven Improvement
After a feature passes its spec requirements, use Andrej Karpathy's auto-research methodology to autonomously discover improvements. This is not unstructured brainstorming — it is a disciplined experiment loop that produces measured, defensible results.
For a CAC mission tool, this matters for two reasons:
- Performance — investigators need answers fast. A triage pass that takes 8 hours instead of 2 means children wait longer for help.
- Defensibility — every claimed improvement is backed by a logged, reproducible experiment. When a defense expert asks "how do you know your hash matcher is faster than the previous version?", the answer is a numbered experiment record with before / after measurements and the SHA of the branch that produced them.
The Loop
while improvements_possible:
1. READ — current spec thresholds + benchmark baselines
2. HYPOTHESIZE — one concrete, testable change
3. IMPLEMENT — in an isolated branch or worktree
4. MEASURE — run benchmarks, compare to baseline
5. EVALUATE — keep if better, discard if not
6. RATCHET — update spec floor to new baseline if merged
The agent runs this loop. The investigator reviews each ratchet decision before it is merged.
Rules
1. Always Measure, Never Guess
- Every hypothesis MUST have a measurable prediction ("this change should improve throughput by ~15%" or "this should reduce false positives below 0.5%").
- Run the actual benchmarks. Do not eyeball code and declare it faster.
- Record before / after numbers with the same workload, same hardware profile, and same measurement methodology. A faster benchmark on a different machine proves nothing.
2. One Variable at a Time
- Each experiment changes exactly one thing: an algorithm, a buffer size, a parallelism strategy, a data structure, a model checkpoint, a confidence threshold.
- Do not bundle multiple changes into one experiment. If you change two things and the metric improves, you cannot attribute the improvement to either change.
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.
- 8d ago First seen · 127 lines · 1,682 tokens per session scan A bd46496c870a
auto-research is a cursor rule published in the GitHub repository Project-VIC-International/Agentic-AI-Development-Course (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 1,682 tokens to every session, about $0.0084 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.