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 commands/fmflurry/settings-opencode/learn-approvegit clone --depth 1 https://github.com/fmflurry/settings-opencodeWhat 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.00007 | $0.00334 |
| Opus 5 | $0.00003 | $0.00167 |
| Sonnet 5 | $0.00001 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
learn-approve 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.
What it actually says
Learn Approve
Approve and apply a staged learning change: $ARGUMENTS
Your Task
The argument is a pending file ID (filename without extension). For example: 1712345678-mistral-pattern.
- Search both
~/.config/opencode/pending/skills/and~/.config/opencode/pending/memory/for the file matching the ID - Read the JSON file
- Based on the
typefield:
If type === "skill"
- Action "create": Create the skill at the appropriate path under
~/.config/opencode/skills/usingskill_manageor file write - Action "patch": Apply the content diff to the existing skill file
- On success: delete the pending file
- Report: "✅ Approved and applied skill: "
If type === "memory"
- Extract each claim from the
claimsarray - For each claim, call
codememory_assert_claimwith the subject/predicate/object/confidence - On success: delete the pending file
- Report: "✅ Approved and applied memory claim(s): "
If the pending file is not found, report: "❌ No pending change found with ID: "
Important
- Do NOT use
codememory_assert_claimfor skill proposals — only for memory claims - Delete the pending file ONLY after successful application
- If application fails, report the error and leave the file for retry
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 · 36 lines · 7 tokens per session scan A 852328ee88f1
learn-approve is a command published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 20d ago), licensed MIT. It adds 7 tokens to every session and 334 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.