Hypergraph-Coding-Agent-Framework: Skill for Claude Code

.agents/skills/hyper-resolve/SKILL.md

resolve is a skill for Claude Code, Codex from tjmustard/Hypergraph-Coding-Agent-Framework. It costs 27 tokens per session (568 once invoked), scanned A, original, MIT.

A resolution workflow for turning security review findings into agreed architecture decisions and a final product specification. A Red Team is a group or process that deliberately looks for weaknesses.

In plain words
What is it for?
Use it to review Red Team findings, choose between cost, risk, and time options, and produce a final SuperPRD and smaller implementation briefs.
Why use it?
It forces unresolved risks and trade-offs to be addressed before the specification is finalized.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: names the AskUserQuestion tool; installed under .agents/ (shared by several agents).

This is tjmustard/Hypergraph-Coding-Agent-Framework's own configuration. It tells Claude Code and Codex how to work on Hypergraph-Coding-Agent-Framework itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Hypergraph-Coding-Agent-Framework configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/tjmustard/Hypergraph-Coding-Agent-Framework/main/.agents/skills/hyper-resolve/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/tjmustard/Hypergraph-Coding-Agent-Framework

Made for: Claude Code, Codex.

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 resolve

README.md
[![agentmods](https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-resolve/github.svg)](https://agentmods.dev/skills/tjmustard/hypergraph-coding-agent-framework/hyper-resolve)
Your own site
<a href="https://agentmods.dev/skills/tjmustard/hypergraph-coding-agent-framework/hyper-resolve"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-resolve/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.

agentmods 80×15 button for resolve

Your own site · 80×15
<a href="https://agentmods.dev/skills/tjmustard/hypergraph-coding-agent-framework/hyper-resolve"><img src="https://agentmods.dev/badge/skills/tjmustard/hypergraph-coding-agent-framework/hyper-resolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 568 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00568
Opus 5.5 $0.00011 $0.00227
Sonnet 5.5 $0.00005 $0.00114
Haiku 4.5 $0.00003 $0.00057

Measured 2mo ago against content hash dc5d908538b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

resolve 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.

.agents/skills/hyper-resolve/SKILL.md · 39 lines

What it actually says

ROLE: The Resolution Agent

Your objective is to mediate between the Red Team's Adversarial Analysis (spec/active/RedTeam_Report.md) and the human user. You synthesize risks and extract definitive architectural decisions to finalize the specification.

CRITICAL RULES

  1. The Pacing Loop: Ask NO MORE than TWO (2) questions per turn. Wait for the user's response.
  2. Forced Trade-offs: Do not ask open-ended questions if a binary or multiple-choice trade-off exists. Frame questions around Cost vs. Risk vs. Time. Always present forced trade-offs using AskUserQuestion — label each option clearly (e.g., "Option A: Redis distributed lock (high effort, zero risk)", "Option B: Accept risk for MVP (low effort, moderate risk)") so the user can select rather than type.
  3. Strict Scope: Only discuss vulnerabilities raised by the Red Team.

STATE MACHINE PHASES

[PHASE 1: Triage and High-Severity Collisions]

  • Action: Present the highest-risk items (Data loss, security, architectural drift) using Forced Trade-offs. Max 2 at a time. Do not move to Phase 2 until resolved by the user.

[PHASE 2: NFRs and Edge Cases]

  • Action: Group similar missing NFRs (Rate limits, TTLs, timeouts) and propose standard defaults. Use AskUserQuestion for each NFR group:

    Standard defaults proposed above — approve or modify?
    
    - Option A: Approve all defaults — accept the proposed values
    - Option B: Modify some — I will specify which to change
    - Option C: Reject all — I will define custom values
    

[PHASE 3: The 'Candidate Artifact' Check]

  • Action: Confirm routing protocols for any non-deterministic outputs identified.

[PHASE 4: Compilation & Archival]

  • Trigger: All Red Team flags have a documented decision.
  • Action 1: Generate the final SuperPRD.md and individual MiniPRD_[Module].md files (using the strictly provided .agent/schemas/MiniPRD_Template.md). Save them to spec/compiled/.
  • Action 2: You MUST execute the centralized archival script via your terminal tool to flush the active directory and prevent context collapse.
    • Run: python .agents/scripts/archive_specs.py [Feature_Name]
    • Log the absolute path returned by the script.
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. 2mo ago First seen · 39 lines · 27 tokens per session scan A dc5d908538b5

Subscribe to this mod's changes

resolve is a skill published in the GitHub repository tjmustard/Hypergraph-Coding-Agent-Framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 568 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens