goal

goal is a command for Claude Code from frontier-infra/adl. It costs 15 tokens per session (852 once invoked), scanned A, original, MIT.

A command that opens a goal contract: a manifest defining how a piece of work will be judged before the work begins.

In plain words
What is it for?
Use it to create task identifiers, choose the responsible role, define completion checks, and restrict which files may be changed.
Why use it?
It turns a vague request into explicit checks and file boundaries, so workers know what completion means and reviewers can verify it consistently.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/frontier-infra/adl/goal
Clone the repo
git clone --depth 1 https://github.com/frontier-infra/adl

Made for: Claude Code.

Wrote 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.

agentmods badge for goal

README.md
[![agentmods](https://agentmods.dev/badge/commands/frontier-infra/adl/goal.svg)](https://agentmods.dev/commands/frontier-infra/adl/goal)
Your own site
<a href="https://agentmods.dev/commands/frontier-infra/adl/goal"><img src="https://agentmods.dev/badge/commands/frontier-infra/adl/goal.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 852 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00852
Opus 5 $0.00008 $0.00426
Sonnet 5 $0.00003 $0.00170
Haiku 4.5 $0.00002 $0.00085

Measured 4d ago against content hash 1126e85a8211, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 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.

.claude/commands/goal.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Open a new /goal contract. The manifest you write becomes the binding success criterion for whatever work follows. Workers cannot report done until Warden verifies against this manifest and writes a sign-off proof.

What to do

  1. Pick a task-id. Format: YYYYMMDD-<slug>-<4hex>. Slug is 2-5 words from the goal, kebab-case. Hex is 4 random characters to disambiguate.

  2. Resolve the role and project. Based on the goal text and .claude/orchestrator/ARGENT.md routing rules, decide which role (forge / quill / scout) will execute the slice and which project overlay applies. If either is unclear, ask the operator. Do not guess.

  3. Translate the goal into machine checks. For each thing the operator implied, write one done_when entry. Prefer test and command checks. Fall back to file_exists / file_contains for documentation slices. Use human_review only when the goal is genuinely subjective (Scout findings, design decisions) — and then state explicitly what the reviewer should confirm.

  4. Add diff constraints when scope matters. If the operator named specific files, populate diff_constraint.touches_only. If files must not be touched (auth, billing, schema migrations are common), populate forbidden. Skip both for documentation-only slices.

  5. Write the manifest to .claude/goals/<task-id>.yaml. Create the directory if it does not exist.

  6. Surface the manifest back to the operator before dispatching anything. If a done_when check is fuzzy ("works correctly," "is fast enough"), say so and ask the operator to tighten it. A vague manifest is worse than no manifest — it gives Warden license to rubber-stamp.

Manifest schema

id: <task-id>
created: <ISO-8601>
operator: <operator name or '@me'>
slice: <one-line description>
role: forge | quill | scout
project: <PROJECT_*.md or 'none'>
base_ref: <git ref to diff against, default: HEAD>
goal: <imperative sentence — what 'done' looks like>
done_when:
  - name: <human-readable check name>
    type: test | command | file_exists | file_contains | diff_constraint | human_review
    # type-specific fields below
    # test:
    command: <test-runner command>
    expect_pass: true
    # command:
    command: <shell command>
    expect_exit: 0
    # file_exists:
    path: <path>
    # file_contains:
    path: <path>
    pattern: <regex or literal>
    # diff_constraint:
    touches_only: [<glob>, ...]
    forbidden: [<glob>, ...]
    # human_review:
    description: <what the reviewer is confirming>
constraints:  # optional — non-negotiable rules carried from project overlay
  - <one-liner>

Read the full file on GitHub · 69 lines

Changes

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.

  1. 4d ago First seen · 69 lines · 15 tokens per session scan A 1126e85a8211

Subscribe to this mod's changes

goal is a command published in the GitHub repository frontier-infra/adl (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 852 once invoked, about $0.0001 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-31.