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/specify)<a href="https://agentmods.dev/commands/athola/claude-night-market/specify"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/specify/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/specify"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/specify.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.00015 | $0.02588 |
| Opus 5 | $0.00008 | $0.01294 |
| Sonnet 5 | $0.00003 | $0.00518 |
| Haiku 4.5 | $0.00002 | $0.00259 |
Grade A, and why
specify 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 5d 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Attune Specify Command
Transform project briefs into structured, testable specifications with functional requirements and acceptance criteria.
When To Use
Use this command when you need to:
- Transform brainstorm output into detailed specification
- Create testable requirements from project brief
- Define acceptance criteria for implementation
- Document functional and non-functional requirements
- Establish scope boundaries before planning
When NOT To Use
Avoid this command if:
- Still exploring problem space (use
/attune:brainstormfirst) - Already have detailed specification (use
/attune:blueprintinstead) - Need to refine existing spec (edit specification document directly)
- Making architectural decisions without requirements (brainstorm first)
Usage
# Create specification from brainstorm output
/attune:specify
# Specify with custom input
/attune:specify --input docs/project-brief.md
# Generate specification for specific feature
/attune:specify --feature "user authentication"
What This Command Does
- Loads project brief from brainstorm phase
- Invokes specification skill with spec-kit integration
- Generates detailed requirements using structured format
- Creates testable acceptance criteria
- Produces specification document for planning phase
Integration with Spec-Kit
When spec-kit plugin is available:
- Uses
Skill(spec-kit:spec-writing)for specification methodology - Applies structured requirement templates
- Ensures testable acceptance criteria
Without spec-kit:
- Falls back to attune's native specification skill
- Provides similar step-by-step approach
- Documents requirements systematically
Workflow
# 1. Invoke specification skill
Skill(attune:project-specification)
# 2. Transform brief into structured spec:
# - Functional requirements
# - Non-functional requirements
# - Acceptance criteria
# - Technical constraints
# - Dependencies
# 3. Generate specification document
# - Saved to docs/specification.md
# - Includes all requirements with testability
# 4. Workflow auto-continues (see below)
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.
- 5d ago First seen · 411 lines · 15 tokens per session scan A 30d4edfb0329
specify is a command published in the GitHub repository athola/claude-night-market (336 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 2,588 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.