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.
npx agentmods add instructions/cass-2003/local-workflow-skill/claude-mdgit clone --depth 1 https://github.com/cass-2003/local-workflow-skillWrote 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/instructions/cass-2003/local-workflow-skill/claude-md)<a href="https://agentmods.dev/instructions/cass-2003/local-workflow-skill/claude-md"><img src="https://agentmods.dev/badge/instructions/cass-2003/local-workflow-skill/claude-md.svg" alt="Measured on agentmods" 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 | $0.00857 | $0.00857 |
| Opus 5 | $0.00428 | $0.00428 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
local-workflow-skill 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This repository is the source workspace for Portable Agent Workflow: a generic, Markdown-first workflow framework and curated skill library for multiple coding agents.
Claude Code should treat this file as a thin project entry. The workflow truth
lives in framework/core/; repository state lives in state/.
Default Workflow
For substantial work, follow:
scan -> state restore -> intent -> authority -> route -> execute -> validate -> sync -> deliver -> evolve
Read:
framework/core/01-workflow.mdframework/core/02-state-systems.mdframework/core/03-routing.mdframework/core/04-authority.mdframework/core/05-validation.mdframework/core/06-evolution.mdframework/core/07-artifact-contracts.mdframework/core/08-autonomous-project-loop.md
Update state/LOG.md, state/REQUIREMENTS.md, state/MEMORY.md, and
state/PROGRESS.md when repository truth changes.
Before substantial work, choose a Context Mode and produce a State Restore
summary from the minimum sufficient sources: context capsule/latest progress,
recent log entries, relevant memory/requirements sections, and changed files.
Use full four-state reads only for first handoff, stale/conflicting state,
high-risk workflow changes, or explicit broad audits. The summary must include
context mode, state sources, stale/placeholders, latest goal, latest validation,
blocker, and current assumptions. If placeholders or stale entries remain,
replace what can be confirmed from repository facts before editing workflow
behavior.
Artifact Contracts
Do not leave substantial audit, acceptance, implementation, fix, validation, or docs-sync work only in chat.
- For
audit/acceptance/验收预检, create or update a report underdocs/audit/when the target project has that directory, and updatedocs/audit/INDEX.md. - For implementation or fixes, update the relevant state files, especially
state/LOG.mdandstate/PROGRESS.md; update docs when behavior, usage, architecture, validation, or risk changes. - For docs changes, update
docs/INDEX.mdor the relevant directory index so new files are discoverable. - Before commit, confirm validation evidence, state sync, index sync, and
git status; split multiple logical changes into multiple atomic commits.
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.
- 4d ago First seen · 86 lines · 857 tokens per session scan A 731cc42429b8
local-workflow-skill CLAUDE.md is an instructions file published in the GitHub repository cass-2003/local-workflow-skill (12 stars, last pushed 1mo ago), licensed MIT. It adds 857 tokens to every session, about $0.0043 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.