project-status CLAUDE.md

project-status CLAUDE.md is an instructions file for coding agents from Openly-Useful/project-status. It costs 516 tokens per session, scanned A, original, Apache-2.0.

A set of working instructions for the Project Status repository, which contains tools for showing whether projects are ready and supported by evidence. It defines repository boundaries, approved paths, validation, and release rules.

In plain words
What is it for?
Use it when modifying Project Status, validating changes, regenerating its host wrappers, or preparing a handoff.
Why use it?
It prevents accidental changes to protected data, generated files, public outputs, releases, or marketplace state.

Instructions file

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.

agentmods
npx agentmods add instructions/openly-useful/project-status/claude-md
Clone the repo
git clone --depth 1 https://github.com/Openly-Useful/project-status

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.

agentmods badge for project-status CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/openly-useful/project-status/claude-md.svg)](https://agentmods.dev/instructions/openly-useful/project-status/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/openly-useful/project-status/claude-md"><img src="https://agentmods.dev/badge/instructions/openly-useful/project-status/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 516 This file is loaded in full into every session.
When invoked 516 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00516 $0.00516
Opus 5 $0.00258 $0.00258
Sonnet 5 $0.00103 $0.00103
Haiku 4.5 $0.00052 $0.00052

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

Security

Grade A, and why

project-status CLAUDE.md 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.

CLAUDE.md · 43 lines

How it starts

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

Claude project instructions

Read AGENTS.md and README.md before changing this repository.

Repository boundary

  • This repository contains only the Project Status product, canonical skill, generated host wrappers, optional read-only MCP companion, dashboard, tests, and release tooling.
  • Do not add owner business records, domain inventories, legal identities, addresses, account information, credentials, local home-directory paths, or unpublished portfolio details.
  • Public projections must remain allowlisted and sanitized. Raw internal evidence locators must never be returned from the MCP or browser APIs.
  • Do not publish, deploy, install a plugin, create a release, change marketplace state, schedule monitoring, commit, or push unless the owner explicitly authorizes that action.

Canonical paths

  • Edit skill behavior only under skill/project-status.
  • Regenerate host wrappers with node scripts/release-sync.mjs sync; do not edit generated wrapper copies directly.
  • Treat .project-status/manifest.json as the repository-local status source of truth.
  • The optional MCP companion must remain read-only, self-contained in release archives, and model/host agnostic.

Validation

After relevant changes, run:

node scripts/release-sync.mjs check
node scripts/release-check.mjs --json
npm test
claude plugin validate .claude-plugin/marketplace.json
claude plugin validate plugins/claude/project-status

Release checks distinguish local distribution readiness from public publication readiness. Never describe pending license, third-party notice, publisher, deployment, or marketplace gates as complete without direct evidence.

First-session handoff acceptance

Before continuing work in a newly authenticated Claude session:

  1. Read this file, AGENTS.md, and README.md.
  2. Run only read-only orientation checks first: git status --short, git remote -v, claude plugin list, npm run status:validate, and node scripts/release-check.mjs --json.
  3. Confirm the repository is the public Openly-Useful/project-status source and that the installed Project Status plugin is enabled.
  4. Report any drift or failure before editing.
  5. When the adjacent local business-planning directory is explicitly available, read its PRIVATE_DATA_POLICY.md and claude-continuation.md, but do not open its private subdirectory unless the owner directly requests a specific private record.
  6. If acceptance passes, summarize the product and privacy state, then continue the guided owner decision queue one question at a time.

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

  1. 5d ago First seen · 43 lines · 516 tokens per session scan A 1c22183c92de

Subscribe to this mod's changes

project-status CLAUDE.md is an instructions file published in the GitHub repository Openly-Useful/project-status (0 stars, last pushed 13d ago), licensed Apache-2.0. It adds 516 tokens to every session, about $0.0026 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.