Agent-Workflow-Kit CLAUDE.md

A CLAUDE.md instruction file for Agent-Workflow-Kit, a project that coordinates coding rules, workflows, agent roles, and checks.

In plain words
What is it for?
It is for guiding Claude through building, planning, design review, full review, audits, model choice, and project improvements.
Why use it?
It tells Claude how to understand the project and which workflow commands and rules govern implementation and review.

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/bita71/agent-workflow-kit/claude-md
Clone the repo
git clone --depth 1 https://github.com/Bita71/Agent-Workflow-Kit
Per session 435 This file is loaded in full into every session.
When invoked 435 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 $0.00435 $0.00435
Opus 5 $0.00217 $0.00217
Sonnet 5 $0.00087 $0.00087
Haiku 4.5 $0.00044 $0.00044

Measured yesterday against content hash 9b35c59c4b1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Agent-Workflow-Kit 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 yesterday.

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 · 42 lines

What it actually says

Claude Adapter

docs/ai is the source of truth for this project. Before working, read:

  • .agent-workflow-kit/config.conf — project settings and active profiles.
  • docs/ai/README.md — map of the AI surface.
  • docs/ai/rules/project.md — tool-agnostic invariants.
  • docs/ai/rules/coding-rules.md — this stack's conventions.
  • docs/ai/rules/commit-message.md — Conventional Commits.

<check> means CHECK_COMMAND from the config. Run it after substantive changes unless it is none. Do not commit or push without an explicit request.

Claude's role

Claude is the primary builder and design reviewer, and the orchestrator for the full pipeline.

Workflows (slash commands in .claude/commands/, each pointing into docs/ai):

  • /symphony — drive the whole task through the pipeline.
  • /build — implement a task.
  • /codex-plan — orchestrate planning through Codex.
  • /review-full — parallel correctness/security + design review.
  • /review-design — design review only.
  • /choose-model — recommend a model/effort.
  • /learn — propose durable repo improvements.
  • /ai-audit, /deps-audit, /apply-worktree.

Rules

  • For implementation, follow docs/ai/agents/build.md and docs/ai/skills/build.md.
  • For design review, follow docs/ai/agents/review-design.md.
  • Do not plan by hand: planning is Codex's job — orchestrate it via /codex-plan.
  • Do not do correctness/security review by hand: that pass is Codex's, inside /review-full.
  • Take Codex/Claude CLI invocations only from docs/ai/agents/cli.md — do not invent flags.
  • Run the configured CHECK_COMMAND after substantive changes.
  • Do not commit or push without an explicit request.
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. yesterday First seen · 42 lines · 435 tokens per session scan A 9b35c59c4b1f

Subscribe to this mod's changes

Agent-Workflow-Kit CLAUDE.md is an instructions file published in the GitHub repository Bita71/Agent-Workflow-Kit (1 stars, last pushed 1mo ago), licensed MIT. It adds 435 tokens to every session, about $0.0022 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.