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/dryvist/ai-workflows/agents-mdgit clone --depth 1 https://github.com/dryvist/ai-workflowsWhat 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.01766 | $0.01766 |
| Opus 5 | $0.00883 | $0.00883 |
| Sonnet 5 | $0.00353 | $0.00353 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
ai-workflows AGENTS.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 3d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-workflows
Reusable AI agent workflows for GitHub Actions. Consumer repos call these with thin ~10-20 line callers.
Architecture
This repo is the single source of truth for CI/CD automation workflows.
Each workflow is a GitHub reusable workflow (on: workflow_call) that consumer
repos invoke via uses: dryvist/ai-workflows/.github/workflows/<name>.yml@main.
Directory Structure
.github/
prompts/
*.md # Prompt files (one per workflow)
scripts/
render-prompt.sh # Shared: envsubst + GITHUB_OUTPUT
best-practices/ # Extracted JS scripts per workflow
ci-fail-issue/
ci-fix/
dep-review/
issue-backlog-sweep/
issue-linker/
issue-resolver/
notification/
post-merge-docs-review/
post-merge-tests/
release-notes/
review-thread-resolver/
shared/
verification/
workflows/
*.yml # Pure YAML workflow definitions (no embedded content)
Workflow Types
All AI workflows use the shared run-ai-agent adapter. The adapter selects
Claude or Codex from GH_ACTION_AI_AGENT and defaults to Claude.
Non-AI utility workflows (notify-ai-pr, ci-fail-issue,
review-thread-resolver) use plain actions/github-script — see
docs/PATTERNS.md "Non-AI Utility Workflow Pattern".
- Prompts rendered via
render-prompt.sh+ step output (envsubst) - Static prompts: most workflows
- Dynamic prompts (ci-fix, post-merge-tests, post-merge-docs-review):
render-prompt.shwith named env vars - Write workflows (code-simplifier, next-steps, post-merge-*, ci-fix,
issue-resolver, pr-review-responder): the selected agent only edits files and
writes typed handoffs (no git or GitHub mutations). A fresh publisher job
lands a GitHub-VERIFIED commit/PR via
createCommitOnBranch(sharedscripts/shared/verified-commit.js). This is mandatory — nativeuse_commit_signingcannot target a branch on our workflow_run/issues/schedule/dispatch triggers. See docs/PATTERNS.md "Verified Commit & PR Pattern".
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.
- 3d ago First seen · 190 lines · 1,766 tokens per session scan A b960c9dfaddc
ai-workflows AGENTS.md is an instructions file published in the GitHub repository dryvist/ai-workflows (5 stars, last pushed 4d ago), licensed MIT. It adds 1,766 tokens to every session, about $0.0088 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
claude-prompts-mcp CLAUDE.md
Claude Code instructions for minipuft/claude-prompts-mcp, covering claude prompts mcp -- operator handbook, core principles, node.js support boundaries, validation gates (one contract, impact-aware subsets) and fleet standards upstream (minipuft/repository-standards).
claude-prompts-mcp AGENTS.md
AGENTS.md instructions for minipuft/claude-prompts-mcp, covering agent rules · claude prompts mcp, canonical ownership and loading, core principles, node.js support boundaries and validation gates (one contract, impact-aware subsets).
scrub-mcp AGENTS.md
AGENTS.md instructions for zombat/scrub-mcp, covering s.c.r.u.b. agent instructions, prime directive, prohibited actions (the bash ban), division of labor and context gathering rules (map-then-navigate).
dxkit CLAUDE.md
Instructions for vyuh-labs/dxkit, covering claude.md — dxkit development rules, architecture rules, 1. tool invocation goes through the registry, 2. never duplicate tool invocation logic and 3. language facts come from detect.ts.
mcp-server-powerpoint code-review.instructions.md
Instructions for sbroenne/mcp-server-powerpoint, covering copilot code review, interop and resource safety, contract and path completeness and protocol, tests, and user-facing surfaces.
ai-marketplace AGENTS.md
Instructions for Kong/ai-marketplace, covering skill authoring guide, what belongs here, before you create a skill, what a good skill does and layered skill design.