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/editnpx skills add skyllwt/AutoSci --skill editgit clone --depth 1 https://github.com/skyllwt/AutoSciWhat 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.00016 | $0.00429 |
| Opus 5 | $0.00008 | $0.00215 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
edit 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
/edit
Add or remove raw sources, or update wiki content, per user request.
Trigger
User manual: /edit <user request>
Inputs
User request, for example:
- "Download this paper to raw/papers/"
- "Delete raw/papers/xxx.pdf"
- "Update the SOTA tracker in topics/efficient-llm-adaptation"
- "Add a new variant to concepts/lora"
Outputs
Updated wiki files, index.md, log.md
Steps
STEP 1: Parse User Intent
- Add raw sources:
- If the user provides a local path: copy to the corresponding directory under
raw/ - If the user provides an arXiv URL: download to
raw/papers/ - If the user provides a web URL: fetch content with markdownify and save to
raw/web/
- If the user provides a local path: copy to the corresponding directory under
- Delete raw sources:
- Confirm then execute deletion
- Update wiki:
- Read the relevant pages and modify content per user instructions
STEP 2: Execute Updates
- Newly added raw sources can later be incorporated into the wiki via
/ingest - Direct wiki modifications: update the specified fields/content in specific pages per user instructions
- When writing forward links, simultaneously write reverse links
STEP 3: Update Navigation
EDIT wiki/index.md: update relevant entriesAPPEND wiki/log.md:## [{date}] update | {description}
STEP 4: Report
- List all changes made
- Suggest follow-up actions (e.g. ingest newly added raw sources if applicable)
Constraints
raw/is read-only for existing files (this skill may add files toraw/, but must not modify existing ones)- Wiki modifications must follow template structure
- Bidirectional links must be kept in sync
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 · 61 lines · 16 tokens per session scan A d6ef90f3da81
edit is a skill published in the GitHub repository skyllwt/AutoSci (1,659 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 429 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…