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/justify)<a href="https://agentmods.dev/commands/athola/claude-night-market/justify"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/justify/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/justify"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/justify.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.00030 | $0.00324 |
| Opus 5 | $0.00015 | $0.00162 |
| Sonnet 5 | $0.00006 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
justify 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 6d 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.
What it actually says
Justify Changes
Post-implementation audit that forces honest accounting of every change. Detects AI additive bias, test-logic tampering, and unnecessary complexity.
Usage
# Justify all changes on the current branch
/justify
# Justify only staged changes
/justify --scope staged
# Justify specific files
/justify src/auth.py tests/test_auth.py
What It Does
- Loads the justify methodology:
Skill(imbue:justify) - Gathers the change delta (git diff from base branch)
- Computes an additive bias score
- Checks Iron Law compliance (test logic tampering)
- Runs minimal intervention analysis per file
- Generates a justification report with risk assessment
When to Use
- After completing implementation, before committing
- Before creating a PR
- When scope-guard flags RED or YELLOW zone
- After any session where significant code was added
Arguments
| Argument | Description |
|---|---|
--scope staged |
Only audit staged changes |
--scope branch |
Audit all branch changes (default) |
--scope file |
Audit specific files listed after |
path... |
Specific file paths to audit |
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.
- 6d ago First seen · 54 lines · 30 tokens per session scan A 75b31b8deba2
justify is a command published in the GitHub repository athola/claude-night-market (337 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 324 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-09-03.
Other commands, from other repositories
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
gsd:pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
git-push
IMPORTANT: This command ONLY runs when explicitly invoked via /git-push. Do NOT auto-push after commits or modifications. Wait for user to explicitly run /push.
commit-push-pr
You are executing the commit-push-pr workflow - the most frequently used inner-loop command.
pr-risk
Calculate a composite PR risk score (size, complexity, test coverage, dependencies, security) before merging or reviewing. Detects large PRs needing splits and generates a context-aware pre-merge checklist. Run before /review-pr or before opening a PR. Usage: /pr-risk [branch or commit range] (default: HEAD1..HEAD).