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 skills add opencue/cuecards --skill vc-autoresearchgit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/skills/opencue/cuecards/vc-autoresearch)<a href="https://agentmods.dev/skills/opencue/cuecards/vc-autoresearch"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/vc-autoresearch.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.00034 | $0.01515 |
| Opus 5 | $0.00017 | $0.00758 |
| Sonnet 5 | $0.00007 | $0.00303 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade A, and why
vc:autoresearch 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 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.
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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vc:autoresearch — Autonomous Optimization Loop
Constraint + Mechanical Metric + Fast Verification = Autonomous Improvement
When to Use
- Improve a measurable metric (test coverage, bundle size, ESLint errors, Lighthouse score, etc.)
- Autonomous execution over N iterations without manual intervention
- Git-tracked experiments where you want rollback on regression
- Exploring a search space of code changes with consistent evaluation
When NOT to Use
| Situation | Better Tool |
|---|---|
| Subjective goals ("make it cleaner") | execute-agent with an approved plan |
| Bug fixing with known root cause | debugger + execute-agent |
| One-shot tasks, no repetition needed | execute-agent |
| No mechanical metric to measure progress | normal RIPER flow instead of autoresearch |
| Files outside a defined scope | manual approach |
Configuration Format
Parsed from user message. Missing required fields trigger a batched AskUserQuestion.
Required
| Field | Description | Example |
|---|---|---|
Goal |
Human description of what to improve | "Increase test coverage in src/utils" |
Scope |
Glob pattern(s) for editable files | "src/utils/**/*.ts" |
Verify |
Shell command that outputs a single number | "npx jest --coverage --json | jq '.coverageMap | .. | .s? | to_entries | map(.value) | (map(select(.>0)) | length) / length * 100' | tail -1" |
Optional
| Field | Default | Description |
|---|---|---|
Guard |
none | Regression check command (exit 0 = pass) |
Iterations |
10 | Maximum iterations to run |
Noise |
medium | Tolerance for metric variance: low / medium / high |
Min-Delta |
0 | Minimum improvement to count as progress |
Direction |
higher | Whether higher or lower metric value is better |
Interactive Setup
When required fields are missing, ask all at once:
AskUserQuestion({
questions: [
{ question: "What metric do you want to improve? (e.g. 'test coverage in src/utils')", field: "Goal" },
{ question: "Which files may be edited? (glob, e.g. 'src/utils/**/*.ts')", field: "Scope" },
{ question: "Verify command — must print a single number to stdout", field: "Verify" },
{ question: "Guard command for regression check? (optional, press Enter to skip)", field: "Guard" }
]
})
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 154 lines · 34 tokens per session scan A 71a071e5faf0
vc:autoresearch is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,515 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
generate-tests
Generate comprehensive tests for a file or function.
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
run-affected-test-file-in-isolation-and-in-co-run-with-its-test-
When delegating a task affected by this skill, include.
use-internals-di-seam-pattern-for-test-injectable-functions
When delegating a task affected by this skill, include.
merge-queue-readiness
Pre-queue merge-group CI simulation. Triggered before adding a PR to a GitHub merge queue. Prevents merge-queue kick-outs from integration test failures.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.