An interactive workflow for updating a project's written goals, success measures, exclusions, and constraints before a later review.

Use it to inspect, refresh, or selectively edit .review/aims.md without running the full Crucible review.

It keeps future project reviews aligned with the current direction instead of relying on outdated aims.

aims — Skill for Claude Code by hazarsozer

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.

Any agent

npx skills add hazarsozer/crucible-cc --skill aims

Clone the repo

git clone --depth 1 https://github.com/hazarsozer/crucible-cc

Made for: Claude Code.

Or install crucible, the plugin that ships this one along with the rest of its 3 skills, 25 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hazarsozer/crucible-cc/aims/github.svg)](https://agentmods.dev/skills/hazarsozer/crucible-cc/aims)

Your own site

<a href="https://agentmods.dev/skills/hazarsozer/crucible-cc/aims"><img src="https://agentmods.dev/badge/skills/hazarsozer/crucible-cc/aims/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hazarsozer/crucible-cc/aims"><img src="https://agentmods.dev/badge/skills/hazarsozer/crucible-cc/aims.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 828 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00047	$0.00828
Opus 5	$0.00023	$0.00414
Sonnet 5	$0.00009	$0.00166
Haiku 4.5	$0.00005	$0.00083

Measured 8d ago against content hash 1aa6be07a05f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

aims 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 8d 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.

skills/aims/SKILL.md · 76 lines

How it starts

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

/crucible:aims — Refresh Project Aims

Force the Profiler agent to re-interview the user about project aims and rewrite .review/aims.md. Useful when the project's goals have shifted between reviews — for example, after a pivot, a new milestone, or a change in stakeholder priorities.

This skill does NOT run a full review. It only refreshes the aims file. To run a review against the refreshed aims, invoke /crucible:run afterward.

Steps

Check for existing aims. Look at .review/aims.md.
- If it exists: read its contents and show them to the user, then ask:
```
Current aims at .review/aims.md:

<contents>

Refresh these aims, edit specific sections, or cancel?
(refresh / edit / cancel)
```
  - refresh → run the full Profiler interview (step 2 below).
  - edit → ask which sections (Goal / Success criteria / Non-goals / Constraints / etc.) to update; only re-interview those, then write back the updated file.
  - cancel → exit without changes.
- If .review/aims.md does NOT exist: announce No aims file found — running first-time interview. and proceed directly to step 2.

Dispatch the Profiler in interview-only mode via the Task tool:

Task(
  subagent_type="profiler",
  description="Refresh project aims (interview only)",
  prompt="""

You are running as the Profiler agent in INTERVIEW-ONLY mode. Your full system prompt is at agents/profiler.md.

Working directory

Mode: interview-only

Do NOT cast a committee. Do NOT output a CastingRoster. Your single job for this invocation:

Read the project files briefly to confirm the tech stack (file tree, README, language manifests).
Run the aims interview (3–5 adaptive questions plus any clarifications).
Write a fresh .review/aims.md from the templates/aims.md.tpl skeleton, populating every {{...}} placeholder.
If the project has .git/ but .review/ is not yet ignored, append .review/ to .gitignore (idempotent).
Confirm with the user that the file looks right.

Return: a single line of plaintext describing what was updated. No JSON, no roster. """ )

Read the full file on GitHub · 76 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.

8d ago First seen · 76 lines · 47 tokens per session scan A 1aa6be07a05f

Subscribe to this mod's changes

aims is a skill published in the GitHub repository hazarsozer/crucible-cc (4 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 828 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-31.

Claude Code Planning claude-code-marketplace claude-code-plugin code-quality plugin

rust-skills

Rust best practices — 179 rules across 14 categories for idiomatic, optimized Rust code.

martineserios/thebrana · 23 tokens

top-design

Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…

wondelai/skills · 113 tokens

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…

wondelai/skills · 147 tokens

create-app

Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…

wondelai/skills · 217 tokens

create-business

Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…

wondelai/skills · 211 tokens

clean-architecture

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go"…