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 skills/sjarmak/agent-workflows/diffusenpx skills add sjarmak/agent-workflows --skill diffusegit clone --depth 1 https://github.com/sjarmak/agent-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.00000 | $0.02669 |
| Opus 5 | $0.00000 | $0.01334 |
| Sonnet 5 | $0.00000 | $0.00534 |
| Haiku 4.5 | $0.00000 | $0.00267 |
Grade A, and why
diffuse 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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blast Radius Impact Mapping. Takes a proposed change (diff, migration, dependency upgrade, config change) and spawns N independent agents, each tracing impact through a different propagation path. No agent sees others' findings. Synthesizes into a combined blast radius map showing first-order, second-order, and third-order effects radiating outward from the change point.
Arguments
$ARGUMENTS — format: [N] [path/to/diff or file or inline change description] where N is optional (default: 5, min 3, max 7)
Parse Arguments
Extract:
- agent_count: the optional leading integer (default 5, min 3, max 7)
- change_target: a diff file path, source file path, directory path, branch name, or inline description of the proposed change
If the target is missing or unclear, ask the user to clarify before proceeding.
Phase 1: Understand the Change
Determine the target type and build a precise understanding of what is changing:
- If a diff or patch file: read it and identify every modified file, function, type, and config key
- If a source file or directory: read it and ask the user what change is being made (or check for uncommitted changes via
git diff) - If a branch name: run
git diff main...<branch>(or the appropriate base) to extract the full changeset - If an inline description: parse it for the affected components
Prepare a change summary covering:
- What is changing (the precise modification)
- Where the change originates (files, functions, lines, config keys)
- What type of change this is (code logic, schema migration, dependency upgrade, config change, API contract change, infrastructure change)
- The stated intent of the change (why it is being made)
Present the change summary to the user and confirm before proceeding. Adjust if the user gives feedback.
Phase 2: Spawn Propagation Agents
Launch all N agents in parallel using the Agent tool. Each agent gets the change summary plus a unique propagation path selected from this list (assign sequentially, wrapping if N < 7):
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.
- yesterday First seen · 223 lines · 0 tokens per session scan A 282fc2fca944
diffuse is a skill published in the GitHub repository sjarmak/agent-workflows (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,669 tokens. 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 skills, from other repositories
speckit.specify
Skill "speckit.specify" from caipe-io/ai-platform-engineering, covering user input, outline, quick guidelines, section requirements and for ai generation.
speckit.clarify
Skill "speckit.clarify" from caipe-io/ai-platform-engineering, covering user input and outline.
local-integration-testing
Run end-to-end integration tests with all 15 agents and supervisor in local Docker Compose dev environment. Validates agent discovery, multi-agent routing, checkpoint persistence, and cross-agent follow-up conversations.
release-docs
Generate a combined release blog post for ai-platform-engineering. Produces a single docs/releases/YYYY-MM-DD-release-X-Y-Z.md file containing release notes and the upgrade guide (migration guide) inline. Use when cutting a release, when a user asks "what changed in 0.4.x", or when upgrading their values.yaml to a new…
update-docs
Audit and update all documentation moving parts for ai-platform-engineering. Checks release blog posts, features page, agent docs, homepage version strings, Docusaurus version config, and sidebar completeness. Fixes what is stale and reports what needs manual attention. Use after cutting a release, adding a new agent…
docker-compose-first-install
Validate and repair the OSS first-install Docker Compose path. Use when editing docker-compose.yaml, docker-compose.dev.yaml, .env.example, release image tags, Compose profiles, Keycloak/OpenFGA/RAG defaults, or first-launch UI behavior for local all-in-one installs.