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/udecode/plate/autogoalnpx skills add udecode/plate --skill autogoalgit clone --depth 1 https://github.com/udecode/plateWhat 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.00038 | $0.10337 |
| Opus 5 | $0.00019 | $0.05169 |
| Sonnet 5 | $0.00008 | $0.02067 |
| Haiku 4.5 | $0.00004 | $0.01034 |
Grade A, and why
autogoal 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
14 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.
- assets/templates/docs.md 4.3 KB
- assets/templates/goal-repair.md 3.9 KB
- assets/templates/goal.md 4.8 KB
- assets/templates/major-task.md 4.7 KB
- assets/templates/packs/agent-native.md 942 B
- assets/templates/packs/browser.md 1.7 KB
- assets/templates/packs/docs.md 1.0 KB
- assets/templates/packs/package-api.md 1.2 KB
- assets/templates/task.md 8.5 KB
- README.md 1.6 KB
- scripts/check-complete.mjs 9.4 KB runs code
- scripts/create-goal-scratchpad.mjs 14 KB runs code
- scripts/create-goal-template.mjs 4.9 KB runs code
- scripts/init-templates.mjs 3.4 KB runs code
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 · 1,207 lines · 38 tokens per session scan A d7e0e0879fd6
autogoal is a skill published in the GitHub repository udecode/plate (16,550 stars, last pushed yesterday), with no licence file. It adds 38 tokens to every session and 10,337 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
autogoal
Create, verify, repair, and close durable Codex goals with measurable outcomes, evidence gates, plan templates, blocker handling, completion audits, and goal-backed workflow repair.
components
React component architecture for creating composable, accessible components with data attributes. Use when creating/updating composable components, not for higher-level feature/page components.
react
React patterns with destructured props, compiler optimization, Effects, and Tailwind v4 syntax. ALWAYS use when using React.
autoreview
Pre-commit/ship code review: Codex default; optional Claude, Pi, Droid, Copilot, Cursor, or OpenCode.
resolve-pr-feedback
Resolve GitHub PR review feedback with source-backed triage, fixes, autogoal plan state, mandatory autoreview closeout, replies, and thread resolution.
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.