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 skills/skyllwt/autosci/ideatenpx skills add skyllwt/AutoSci --skill ideategit clone --depth 1 https://github.com/skyllwt/AutoSciWrote 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/skyllwt/autosci/ideate)<a href="https://agentmods.dev/skills/skyllwt/autosci/ideate"><img src="https://agentmods.dev/badge/skills/skyllwt/autosci/ideate.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 | $0.00023 | $0.07420 |
| Opus 5 | $0.00012 | $0.03710 |
| Sonnet 5 | $0.00005 | $0.01484 |
| Haiku 4.5 | $0.00002 | $0.00742 |
Grade A, and why
ideate 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 — 557 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ideate
Generates high-quality research ideas through a 5-phase pipeline, grounded in the wiki knowledge base and external search. Phase 1 scans the research landscape (wiki + WebSearch + S2), Phase 2 runs a dual-model brainstorm (Claude + Review LLM independently), Phase 3 applies first-pass filter + deep validation (feasibility, novelty, review), Phase 4 writes ideas to the wiki (including eliminated ideas, with failure reasons recorded as anti-repetition memory), Phase 5 runs pilot experiments on surviving ideas (idea pages already exist) and updates results.
Inputs
direction(optional): research direction, keywords, or specific problem description. If omitted, automatically selects the most valuable direction from open_questions.md.--max-ideas N(optional, default 3): maximum number of ideas to write to the wiki--skip-validation: skip Phase 3 Step 2 deep validation (skip /novelty and /review; fast mode: first-pass filter only)--skip-pilot: skip Phase 5 pilot experiments (fast mode: Phase 1–4 only)--auto: fully automatic mode, no pause for user confirmation (used when called by /research)
Outputs
wiki/ideas/{slug}.md— one page per idea (status: proposed), covering both top ideas and eliminated ideaswiki/graph/edges.jsonl— new idea → concept/topic relationship edgeswiki/graph/context_brief.md— rebuilt compressed contextwiki/graph/open_questions.md— rebuilt knowledge gap map- IDEA_REPORT (printed to terminal) — pipeline execution summary, ranked results, novelty scores
Wiki Interaction
Reads
wiki/graph/context_brief.md— global contextwiki/graph/open_questions.md— knowledge gaps, drives idea directionwiki/ideas/*.md— existing ideas, especially status=failed ideas and their failure_reason (banlist)wiki/papers/*.md— existing paper methods and resultswiki/concepts/*.md— technical concepts, find cross-domain combination opportunitieswiki/methods/*.md— reusable methods, scope candidate inspirationswiki/topics/*.md— research direction maps, SOTA and open problems (including### Known gapsand### Methodological gaps)wiki/experiments/*.md— existing experiment results, avoid duplication
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 · 557 lines · 0 tokens per session scan A 9fb2d36c0048
ideate is a skill published in the GitHub repository skyllwt/AutoSci (1,659 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 7,420 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…