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 skills add boshu2/agentops --skill craft-goalgit clone --depth 1 https://github.com/boshu2/agentopsWrote 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/boshu2/agentops/craft-goal)<a href="https://agentmods.dev/skills/boshu2/agentops/craft-goal"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/craft-goal/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/boshu2/agentops/craft-goal"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/craft-goal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 245 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.1 | $0.00043 | $0.02440 |
| Opus 5.5 | $0.00017 | $0.00976 |
| Sonnet 5.5 | $0.00009 | $0.00488 |
| Haiku 4.5 | $0.00004 | $0.00244 |
Grade A, and why
craft-goal 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 today.
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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craft Goal
Craft or lint the autonomy contract above AgentOps RPI. A goal is a persistent controller (the Goal / Mayor role) over a bead-shaped experiment graph: each RPI is one scientific trial, and the goal picks the next useful trial, preserves what was learned and ratchets toward a larger outcome.
Goal / Mayor: observe graph → choose bounded wave → consume results → ratchet
└─ Bead: durable experiment intent, context, scratch, evidence, and links
└─ RPI: plan → implement → checks → one fresh validate where a mistake is costly → report
└─ Implementation: one RED → GREEN → refactor experiment
The number of RPIs need not be known in advance. A goal is safe when success is decidable, every experiment is bounded, evidence keeps its provenance, and the authorization envelope cannot silently renew itself. Beliefs are revisable: new evidence may retract an earlier claim. More stored knowledge is neither progress nor proof that knowledge is correct.
Authority boundary. The emitted prompt and safety report are inert caller-owned text. Crafting creates no goal, starts no runtime, mutates no bead and confers no standing authorization. The prompt drives RPI dispatch only when a caller pastes it into their own goal runtime, under their own authority and within the non-renewing envelope they set. Craft Goal reads tracker state when present but needs no tracker installed to compile a prompt.
Modes
| Caller wording | Mode | Result |
|---|---|---|
| "craft a goal", "turn this into a goal" | craft | Decision, then the filled goal prompt and settings when safe. |
| "lint/review this goal", "is this safe" | lint | Decision and findings, plus a rewrite when supplied facts permit one. |
Admission: decide first
Fuzzy route is acceptable; fuzzy success is not. Before goal creation the caller must know the outcome, what evidence would prove it, non-goals, and authority; the exact experiment graph may still be unknown. Write each terminal criterion as a Given/When/Then with an observable result and name each domain term once; the caller can settle these with Interview first.
What ships with it
2 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.
- today Changed · -1 lines · +9 tokens per session 9ba22488f422
- 2d ago Changed · +1 lines fd493748bb50
- 18d ago Changed · -29 lines · -4 tokens per session 0dd04d3b641d
- 20d ago Changed · +34 lines 063d73825aca
- 28d ago Changed · -30 lines 3b00276458dd
- 29d ago Changed · -62 lines 08346b1b4a29
- 1mo ago Changed · +4 lines · -33 tokens per session dfa2ccc417e2
- 1mo ago Changed · +37 lines 7d58a70c1e75
- 1mo ago Changed 5277a9bc3f61
- 1mo ago First seen · 252 lines · 71 tokens per session scan A 9bd382b85413
craft-goal is a skill published in the GitHub repository boshu2/agentops (450 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 2,440 once invoked, about $0.0002 per session on Opus 5.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
create-pull-request
Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
gate-and-merge
Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.
doubt-driven
Use when a non-trivial decision sits under uncertainty and correctness matters more than speed. Not for patch review: use review. Not for plan attacks: use load-bearing-assumption-test.
pr-review-canvas-html
Use when asked to render a GitHub PR as a standalone review HTML page. Fetches PR data via gh API, renders diffs with move detection, and serves the artifact on a local port. Not for Cursor Canvas output — use pr-review-canvas.
resolve
Use when addressing review feedback in analyze or reception mode, or handling GitHub PR feedback in autonomous, interactive, or summary mode for a named PR target. Classifies, applies, replies, or summarizes comments.