Borrowing it
Nothing to install: this file belongs to hachej/boring-ui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hachej/boring-ui/main/.agents/skills/autoresearch/SKILL.mdgit clone --depth 1 https://github.com/hachej/boring-uiWrote 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/hachej/boring-ui/autoresearch)<a href="https://agentmods.dev/skills/hachej/boring-ui/autoresearch"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/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.00022 | $0.00355 |
| Opus 5 | $0.00011 | $0.00178 |
| Sonnet 5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
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 3d 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
Autoresearch
Invocation:
/skill:autoresearch <issue-or-target> goal="<outcome>" [ui=<registered-spec>] [max=<1..5>]
Read ../../../docs/procedures/autoresearch.md, then the regular
../plan/SKILL.md and ../exec/SKILL.md. Autoresearch controls their sequence;
it does not replace their contracts.
- Require a tracked issue, measurable goal, bounded target, exact functional proof, optional exact registered UI spec, and iteration cap (default 3, maximum 5). Resolve missing intent through the plan procedure and stop while any owner decision remains open.
- Apply the plan procedure once. In a dedicated worktree, capture iteration 0 from the unchanged target and bind its evidence to the commit and tree.
- Apply the exec procedure once as the sole writer. Internally repeat the canonical combined-review loop: select at most three ordered findings, fix, prove, and independently re-review the resulting revision. A selected fix spends one iteration even when proof remains red.
- Stop early at
success,stalled, orblocked-owner; otherwise stop after the declared cap ascap-exhausted. Produce one terminal owner handoff and never merge.
Complete only when every iteration is recorded, deterministic proof and reviewer dispositions target the same final revision, the terminal state is explicit, and the owner has a runnable artifact or exact validation path.
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.
- 3d ago First seen · 36 lines · 22 tokens per session scan A 0dc4ce5f6805
autoresearch is a skill published in the GitHub repository hachej/boring-ui (46 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 355 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-09-03.
Other skills, from other repositories
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
gsd-ns-review
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
superlint
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.