Borrowing it
Nothing to install: this file belongs to tjmustard/Hypergraph-Coding-Agent-Framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tjmustard/Hypergraph-Coding-Agent-Framework/main/.agents/skills/hyper-status/SKILL.mdgit clone --depth 1 https://github.com/tjmustard/Hypergraph-Coding-Agent-FrameworkWrote 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/skills/tjmustard/hypergraph-coding-agent-framework/hyper-status)<a href="https://agentmods.dev/skills/tjmustard/hypergraph-coding-agent-framework/hyper-status"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-status/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/skills/tjmustard/hypergraph-coding-agent-framework/hyper-status"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-status.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.00045 | $0.00424 |
| Opus 5.5 | $0.00018 | $0.00170 |
| Sonnet 5.5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
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 2mo 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
Status
This skill immediately outputs the current Living Master Plan — the complete, up-to-date snapshot of project state maintained by the Expert Co-Researcher persona.
When to use this skill
- When the user wants a quick summary of where the project stands.
- When the user explicitly runs
/hyper-status. - At the start of a new session to re-orient before diving in.
- When context has been lost and the user needs to re-establish shared understanding.
How to use it
Read the following files to compile the current state:
.agents/memory/activeContext.md— current focus and next steps.agents/memory/productContext.md— product goals and decisions.agents/memory/systemPatterns.md— architectural patternsspec/compiled/architecture.yml— hypergraph statespec/compiled/SuperPRD.md— system of record
Then output the Living Master Plan immediately, covering all sections without compressing or summarizing older milestones:
Project Objectives
The fundamental goals of the current project — what success looks like.
Current Hypotheses & Architecture
The theoretical foundation and structural plans currently in play. What architectural bets have been made and why.
Actionable Steps
A high-level roadmap where any immediate tasks are broken down into clear atomic steps. Flag what is blocked, in-progress, or ready to start.
Known Constraints & Open Questions
Limitations, barriers, and uncertainties that affect execution. Include both technical constraints and product unknowns.
The Graveyard
A strict, exhaustively detailed log of:
- Failed code iterations and why they failed
- Discarded architectural approaches and what ruled them out
- Disproven hypotheses and the evidence against them
Do not compress this section. The Graveyard prevents repeating known failures.
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.
- 2mo ago First seen · 47 lines · 45 tokens per session scan A 025fba40f005
status is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 424 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…