graphyloop-workflow

graphyloop-workflow is a skill for Claude Code, Codex from chadixearth/graphyloop. It costs 60 tokens per session (1,475 once invoked), scanned A, original, MIT.

A workflow guide for non-trivial coding tasks and multi-file changes. It tells a coding agent to recall relevant project knowledge, prepare context, make a planned change, and verify it by running checks.

In plain words
What is it for?
It is for organising larger coding tasks, coordinating work across several files, and checking the result before reporting completion.
Why use it?
It reduces missed project rules, repeated code discovery, unplanned parallel work, and changes that are not tested. It also produces a record of the work and its evidence.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; mentions AGENTS.md; mentions Codex.

Good fit It is for organising larger coding tasks, coordinating work across several files, and checking the result before reporting completion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chadixearth/graphyloop/graphyloop-workflow
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 chadixearth/graphyloop --skill graphyloop-workflow
Clone the repo
git clone --depth 1 https://github.com/chadixearth/graphyloop

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 graphyloop-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/chadixearth/graphyloop/graphyloop-workflow/github.svg)](https://agentmods.dev/skills/chadixearth/graphyloop/graphyloop-workflow)
Your own site
<a href="https://agentmods.dev/skills/chadixearth/graphyloop/graphyloop-workflow"><img src="https://agentmods.dev/badge/skills/chadixearth/graphyloop/graphyloop-workflow/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 graphyloop-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/chadixearth/graphyloop/graphyloop-workflow"><img src="https://agentmods.dev/badge/skills/chadixearth/graphyloop/graphyloop-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,475 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.00060 $0.01475
Opus 5.5 $0.00024 $0.00590
Sonnet 5.5 $0.00012 $0.00295
Haiku 4.5 $0.00006 $0.00147

Measured 8d ago against content hash 5539229a0bd5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

graphyloop-workflow 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/graphyloop-workflow/SKILL.md · 47 lines

How it starts

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

GraphyLoop Workflow v2 (condensed)

The full rules live in the installed rules file (AGENTS.md) when your harness loads one. This is the same workflow in one page, for harnesses that do not: Oh My Pi, Gemini CLI, Claude Code and others. The user's explicit instruction and the project's own rules always win.

Tool names: OpenCode graphyloop_<tool>; Claude Code and DeepSeek Harness mcp__graphyloop__<tool>; Codex, Cursor, Oh My Pi, Gemini CLI bare <tool>. Below: bare names. If one is missing, run npx graphyloop doctor.

The 11 rules

  1. Recall first, record last. memory_search with 2-4 keywords before planning; use hits, stay silent on a miss, never invent one. At the end memory_store ONE dense line (decision / lesson / pattern / event). Never store credentials. See swarm-memory.
  2. Size the work. 3 or fewer known files: do it inline (read, smallest edit, one targeted check, no dispatch, no memory calls). 4+ files or unmapped code is a build: rules 3-9.
  3. Context pack. One batched read pass writes ctx-<slug>.md: per lane path:line, the current code excerpt, the pattern to copy. Lanes start editing instead of rediscovering.
  4. Freeze the contract. Same turn as dispatch, write contract-<slug>.md (entities and columns, routes with request/response JSON and error codes, props, the test scenarios that define done, env keys). It is the only cross-lane dependency; if wrong, fix the contract, never drift.
  5. One wave. All independent lanes in ONE parallel dispatch, one lane per layer (data, backend, frontend, tests, UI), strictly disjoint file sets, max 4 concurrent by default. Data runs alongside backend and frontend.
  6. Turn economy. Lanes batch reads, first edit by turn 5, done in about 25 turns; 40+ means mis-sized. End every BUILDER brief with: Read the ctx pack and contract first, in ONE turn. Batch 2+ reads/searches into one parallel call; read with line ranges; never re-read a file; first edit by turn 5; do not run project-wide lint/test/build — the driver does. Wave-0 (writes ctx + contract): Batch 2+ reads/searches into one parallel call; read with line ranges; never re-read a file; write the ctx pack and contract before anything else. Integration/verify/deploy lanes: Read the ctx pack and contract first, in ONE turn. Batch 2+ reads/searches into one parallel call; read with line ranges; never re-read a file.
  7. No polling. Servers, builds, deploys and renders run in the background or via the tool's own blocking command (vercel inspect --wait, gh run watch). Never sleep-loop.
  8. Verify by running. Smoke the changed path and quote the decisive output line. Tests alone are not proof; check UI in a real browser; check artifacts by viewing the rendered file. Run lint/typecheck/test/build once, centrally, after lanes land.
  9. Audit is conditional. Reviewer and security agents only for auth, RBAC, payments, uploads, secrets, data/tenant boundaries, or a diff you cannot read end to end.
  10. Artifact wave (posters, decks, PDFs, video): freeze brief-<slug>.md, hero piece first, one lane per artifact.
  11. Evidence-first report: Changed / Files / Verified (command plus verbatim output) / Skills / Blocked. Never claim a check that did not run.

Read the full file on GitHub · 47 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. 8d ago First seen · 47 lines · 60 tokens per session scan A 5539229a0bd5

Subscribe to this mod's changes

graphyloop-workflow is a skill published in the GitHub repository chadixearth/graphyloop (3 stars, last pushed 9d ago), licensed MIT. It adds 60 tokens to every session and 1,475 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-10-09.