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/cobusgreyling/loop-engineering/goal-verifiernpx skills add cobusgreyling/loop-engineering --skill goal-verifiergit clone --depth 1 https://github.com/cobusgreyling/loop-engineeringWrote 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/cobusgreyling/loop-engineering/goal-verifier)<a href="https://agentmods.dev/skills/cobusgreyling/loop-engineering/goal-verifier"><img src="https://agentmods.dev/badge/skills/cobusgreyling/loop-engineering/goal-verifier.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.00008 | $0.00017 |
| Opus 5 | $0.00004 | $0.00009 |
| Sonnet 5 | $0.00002 | $0.00003 |
| Haiku 4.5 | $0.00001 | $0.00002 |
Grade A, and why
goal-verifier 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.
What it actually says
Verifier
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 · 5 lines · 8 tokens per session scan A 1e1a61a4abd8
goal-verifier is a skill published in the GitHub repository cobusgreyling/loop-engineering (10,896 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 17 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 skills, from other repositories
use-sdk
Install, configure, and use a TypeScript SDK generated with @ama-sdk. Use when user wants to call APIs, set up a client (fetch, Angular, beacon), or understand how to use an existing SDK package.
logic-review
Review existing components, services, or stores for misplaced logic — presenter leaks, componentType mismatches, wrong store variants. Use logic-placement when designing something new.
rxjs-vs-signals
This skill should be used when writing or reviewing reactive code in components, services, or stores — any time a choice is made between using Angular Signals (signal, computed, input, effect) or RxJS Observables (subscribe, pipe, switchMap, async pipe). Guides the decision with Otter-specific patterns.
a11y-keyboard-playwright
Write keyboard-only test variants and focus management checks using Playwright: navigation patterns, focus expectations, helpers, and file structure conventions.
sdk-plugins
Use and create @ama-sdk plugins for request transformation, authentication, resilience, and response processing. Use when user asks about SDK plugins, wants to add auth/retry/timeout, needs to create a custom plugin, or wants to transform requests before sending, wrap the fetch call itself (logging, metrics…
post-pr-review
PR レビュー結果を1回の API コールで1つの Review として GitHub に投稿する。複数のインライン指摘や総括コメントを含むレビューを投稿する場合は必ずこの skill を使うこと。gh pr comment や gh pr review を使った個別投稿は禁止。.