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/satsilem/ai-workflow-framework/claude-mdgit clone --depth 1 https://github.com/satsilem/ai-workflow-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/instructions/satsilem/ai-workflow-framework/claude-md)<a href="https://agentmods.dev/instructions/satsilem/ai-workflow-framework/claude-md"><img src="https://agentmods.dev/badge/instructions/satsilem/ai-workflow-framework/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.00358 | $0.00358 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
ai-workflow-framework 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 5d 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
AI Workflow Framework - Reference
Project: AI Workflow Framework Client/Owner: Maintainers Stack: Markdown, workflow templates, AI agent operational docs Status: Initial scaffold Last Updated: 2026-04-03
Project Structure
| File/Folder | Purpose |
|---|---|
CLAUDE.md |
Master instructions for AI-assisted sessions in this repo |
SESSION.md |
Chronological session log and key learning capture |
TODO.md |
Open and completed tasks |
NOTES.md |
Scratchpad for temporary notes |
INSIGHTS.md |
Workflow improvements and automation ideas |
.ai-notes/ |
Deep-dive reports and incident notes |
.reference/ |
Stable reference documentation |
.tmp/ |
Temporary scripts and working files |
.backups/ |
Local backups |
Stack
- Markdown documentation
- Reusable AI workflow patterns
- Cross-agent instructions and standards
Key Commands
start session- load project context and begin workend session- close session and update operational docsproject setup- initialize missing standard files/folders
Git Workflow
- Branch from
mainusing descriptive branch names - Keep commits focused and descriptive
- Open PRs with encoded context, not just output summaries
Safety Protocols
- Confirm before destructive operations
- Never commit secrets or credentials
- Keep
.tmp/and.backups/out of version control
Last Updated: 2026-04-03 Project Manager: Maintainers Purpose: Master reference for this AI workflow framework repository.
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.
- 5d ago First seen · 62 lines · 358 tokens per session scan A 0b9d58a5643d
ai-workflow-framework CLAUDE.md is an instructions file published in the GitHub repository satsilem/ai-workflow-framework (2 stars, last pushed 5mo ago), licensed MIT. It adds 358 tokens to every session, about $0.0018 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.
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).