What is contract-status?

A command-line status view for feature contracts, showing their current stage, readiness, time remaining against the agreed deadline, and next action.

Use it to inspect one contract or all active contracts, including whether blockers prevent promotion and whether a deadline has passed.

It gives the team one quick, consistent answer about what is in progress and who needs to act, without guessing the phase or deadline.

contract-status — Skill for Claude Code by iampawan

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 iampawan/Manifest --skill contract-status

Clone the repo

git clone --depth 1 https://github.com/iampawan/Manifest

Made for: Claude Code.

Or install manifest, the plugin that ships this one along with the rest of its 28 skills, 15 commands.

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/iampawan/manifest/contract-status.svg)](https://agentmods.dev/skills/iampawan/manifest/contract-status)

Your own site

<a href="https://agentmods.dev/skills/iampawan/manifest/contract-status"><img src="https://agentmods.dev/badge/skills/iampawan/manifest/contract-status.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,375 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.00071	$0.01375
Opus 5	$0.00036	$0.00687
Sonnet 5	$0.00014	$0.00275
Haiku 4.5	$0.00007	$0.00137

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

Security

Grade A, and why

contract-status 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/contract-status/SKILL.md · 127 lines

How it starts

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

Contract status

A quick "where does this stand" view, computed deterministically — no LLM guessing about phase or time. Powered by validate.mjs --status.

Usage

/status <ID> — one contract
/status — every contract currently in flight (status promoted and not yet landed), most-urgent first

One contract

Run:

node <plugin-root>/scripts/validate.mjs --status .manifest/contracts/<ID>.md

It prints (deterministically from the contract frontmatter):

AUTH-12 — Resend OTP on login
  phase:     ② In review
  ⏳ SLA: 23h 14m left (due 2026-05-21 13:30 IST / 2026-05-21 08:00 UTC)
  readiness: review_needed  ·  promotable: ✅ (0 blockers, 2 advisory warnings)
  next:      promote, or address warnings first

Relay it as-is. If --status exits non-zero, the SLA is overdue — call that out. Lead with promotable (0 open blockers) — that's the real gate. When promotable is true, say so even if readiness is review_needed; open warnings are advisory and never block, so a dev isn't stuck. (Read open blocker/warning counts from the latest <ID>.findings.json if present.)

Who holds the ball (PM accountability). If the contract has a pickup.ballLog, compute the ledger — node scripts/ready-check.mjs --ledger <ballLog.json> <slaHrs> <promotedAt> — and lead with it when the ball is with the PM. The SLA is charged only for dev-side time, so report the effective SLA (paused while blocked on PM), not raw elapsed:

🟡 blocked on PM 2d 4h (SLA paused) · dev used 6h/48h · 2 bounces
   → nudge the PM, or proceed on the dev's assumption

This is the anti-blame line: a dev is never shown as overdue for time the PRD gap left the ball with the PM.

All in-flight (the dashboard)

List .manifest/contracts/*.md (exclude .findings.md, .r*.md, .deploy-*, .launch-report-*, .bug-log.md, .decomposition.md, and .fixes/).
For each whose status is promoted and landed is unset, run --status.
Sort by SLA urgency: overdue first, then least time left.
Print a compact table:

Read the full file on GitHub · 127 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 · 127 lines · 71 tokens per session scan A 771125310dbc

Subscribe to this mod's changes

contract-status is a skill published in the GitHub repository iampawan/Manifest (5 stars, last pushed 6d ago), licensed MIT. It adds 71 tokens to every session and 1,375 once invoked, about $0.0004 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.

Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens