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.
git clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/commands/athola/claude-night-market/mission)<a href="https://agentmods.dev/commands/athola/claude-night-market/mission"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/mission/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/commands/athola/claude-night-market/mission"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/mission.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00016 | $0.01828 |
| Opus 5 | $0.00008 | $0.00914 |
| Sonnet 5 | $0.00003 | $0.00366 |
| Haiku 4.5 | $0.00002 | $0.00183 |
Grade A, and why
mission 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.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Attune Mission Command
Orchestrate the entire attune development lifecycle (brainstorm, specify, plan, execute) as a single mission with automatic state detection and recovery.
When To Use
Use this command when you need to:
- Start a new project and run through the full development lifecycle
- Resume an interrupted project workflow from where you left off
- Execute a focused tactical implementation from existing artifacts
- Quick-fix from an existing implementation plan
- Audit, dogfood, or review existing software and produce a findings report
When NOT To Use
Avoid this command if:
- You want to run a single phase without auto-chaining (use
/attune:brainstorm --standalone,/attune:specify --standalone, etc.) - Task is non-project work (debugging, ad-hoc research). Structured
review work is in scope: use
--type review - You need fine-grained control over each phase transition
Note: Individual commands (
/brainstorm,/specify,/blueprint) now auto-chain forward by default. Use--standaloneto run a single phase without continuing. Use/attune:missionwhen you need state persistence, resume support, and damage-control.
Usage
# Auto-detect mission type and start
/attune:mission
# Resume a paused or interrupted mission
/attune:mission --resume
# Override mission type
/attune:mission --type full
/attune:mission --type standard
/attune:mission --type tactical
/attune:mission --type quickfix
/attune:mission --type review
# Custom phase sequence
/attune:mission --phases brainstorm,execute
# Skip user checkpoints between phases
/attune:mission --auto
What This Command Does
- Detects project state: scans for existing artifacts (brief, spec, plan)
- Selects mission type: chooses the appropriate phase sequence
- Routes through phases: invokes
Skill(attune:{phase})for each step - Checkpoints between phases: lets you review, pause, or adjust
- Handles errors: recovers from failures via
leyline:damage-control - Saves mission state: enables resume from any point
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 · 216 lines · 16 tokens per session scan A 03bff03b0eec
mission is a command published in the GitHub repository athola/claude-night-market (337 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 1,828 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-09-03.
Other commands, from other repositories
contact-upsert
Create or update a contact, optionally assign to groups.
github-issue-fix
This is a detailed way you can analyze the GitHub issues and let Claude handle them in best possible way.
spec
A requirements-planning command for OpenSpec, a tool that records software changes as proposals, specification updates, and task lists. It clarifies the request, challenges risky assumptions, and pauses for approval before implementation.
start
Analyze this project and build a GoalT goal tree for it, linking real files and backend artifacts to each goal.
features:add
(Features) Add a new feature to a specific phase.
features:status
(Features) Show implementation status by phase.