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/try-works/recursive-mode/recursive-trainingnpx skills add try-works/recursive-mode --skill recursive-traininggit clone --depth 1 https://github.com/try-works/recursive-modeWhat 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.00034 | $0.01636 |
| Opus 5 | $0.00017 | $0.00818 |
| Sonnet 5 | $0.00007 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
recursive-training 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 2d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
recursive-training
Purpose
Use this skill after a repository has accumulated completed recursive-mode runs and you want to turn repeated successes or failures into durable, repo-local guidance.
The canonical workflow still lives in /.recursive/RECURSIVE.md. This skill owns only the training, loading, and memory-discipline layer that sits around completed runs.
When to use it
Use recursive-training to:
- extract cross-run learnings from completed recursive-mode runs
- keep those learnings in
/.recursive/memory/instead of ad hoc mirrors - refresh memory after Phase 8 locks
- load only the most relevant prior learnings before a new run starts
- provide startup guidance without mutating the memory plane
Hard rules
- Repository-local only. Training data and extracted memory stay inside the current repo.
- No parameter updates. Learning happens through files in
/.recursive/memory/, not model mutation. /.recursive/memory/is the only canonical store. Pointer files are bootstrap-managed and non-authoritative.- All markdown under
/.recursive/run/<run-id>/is eligible training input, not just00-08. - Group runs by subsystem only. The extractor assigns task types per learning item.
- Use contrastive extraction when both winners and losers exist; fall back to winner-only extraction for high-quality repos.
- Every extracted item must remain evidence-grounded in completed runs.
- Training scripts do not own
AGENTS.md; bootstrap owns bridge-file updates.
Training model
recursive-training combines two ideas:
- ReasoningBank-style memory items for structured, reusable extracted guidance
- Training-free GRPO-style comparison for contrastive winner/loser extraction when variance exists
At a high level:
- Parse all markdown artifacts from completed runs.
- Infer the dominant subsystem from changed paths and evidence across those artifacts.
- Classify each subsystem group as contrastive, winner-only, or insufficient.
- Ask the extractor for structured learning items.
- Write those items into:
/.recursive/memory/domains/<subsystem>.md/.recursive/memory/training/<task-type>.md
- Refresh the memory registry/startup guidance without treating pointer files as authoritative memory.
What ships with it
3 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.
- 2d ago First seen · 196 lines · 34 tokens per session scan A f6a9016c7da4
recursive-training is a skill published in the GitHub repository try-works/recursive-mode (129 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,636 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-08-30.
Other skills, from other repositories
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后，主动执行此流程！ 将学到的经验归档为 skill，供以后参考。不要等用户提醒。.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.