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/liuyingxuvka/flowguard/flowguard-development-process-flownpx skills add liuyingxuvka/FlowGuard --skill flowguard-development-process-flowgit clone --depth 1 https://github.com/liuyingxuvka/FlowGuardWrote 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/skills/liuyingxuvka/flowguard/flowguard-development-process-flow)<a href="https://agentmods.dev/skills/liuyingxuvka/flowguard/flowguard-development-process-flow"><img src="https://agentmods.dev/badge/skills/liuyingxuvka/flowguard/flowguard-development-process-flow.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.1 | $0.00020 | $0.00677 |
| Opus 5 | $0.00010 | $0.00338 |
| Sonnet 5 | $0.00004 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
flowguard-development-process-flow 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FlowGuard Development Process Flow
Purpose
Order stages, validation, sync, and release.
Entrypoint Scope
Public owner: public_owner; simulator: execution_freshness, artifact versions,
payload schemas, and conditional process optimization.
Local Material Routing
Read references/development_process_flow_protocol.md; for rough plans,
multi-skill/tool work, or distribution/release load respectively
references/plan_detailing_protocol.md, references/agent_workflow_protocol.md,
or references/distribution_release_protocol.md.
Entrypoint Acceptance Map
Accept stages, versions, owners, evidence; return order/revalidation.
Use When
- Use for staged work, artifact versions, sync, and release claims.
Do Not Use When
- Keep specialists; unclear routing goes to
flowguard.
Required Workflow
- Register stages, writes, evidence, peers, WorkContexts;
plan_detailing_compilerandagent_workflow_rehearsaldetail order. Optimize onlydiagnostic_boundary_choice; isolatesafe_parallel. - Freeze owners
execute|reuse_current|blocked; plan-only starts none. Revalidate affected obligations. One invocation shares observation, source check, leaf publication, and receipt reconciliation. - Order: owner/intent -> lightweight path quality -> deep review -> implementation -> affected validation -> revision -> activation; refresh drift.
- Verify one ModelMaturation receipt; user choice cannot close missing evidence.
- Ordinary work loads affected shards; whole qualification freezes profile/projection identities and freshness.
- Accept one
ModelRevisionSetatomically; delta is not completeCurrentEffectiveIntentView. Write evidence before pointer; freeze release identities before final gate.
Hard Gates
- Model-purpose gate: freeze task-specific failure(s)/claim_boundary; bind native good/bad-per-failure/oracle/current evidence. Reusable types are not fixed-purpose: no mode/fallback; only FlowGuard-declared checks may support completion claims. Require real FlowGuard check engine and AGENTS.md managed record; forbid a fake mini-framework. Activation/reverse share lock/CAS; stale head stops.
- Authorization bounds attempts, not confidence. Unknown owner/impact, active lease, or missing revalidation blocks.
single_clear_pathproceeds directly; an exact deep trigger blocks implementation/activation until closed. Unchanged models reuse exact current results.- ModelMaturation owns path quality; DPF verifies order/currentness. No target-generation step belongs to validation or release.
- Preserve provider, model/path-quality, binding, resource, test, projection, and observed/normative identities. Success is artifact-backed; non-pass is visible.
- Source/model, consumer, install, commit, tag, GitHub Release are separate claims.
- Invocation-local reuse is not authority. Never repeat semantics or scan receipts per leaf; missing freshness/reconciliation is
not_run.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .skillguard/check-manifest.json 109 KB
- .skillguard/compiled-contract.json 133 KB
- .skillguard/contract-source.json 37 KB
- agents/openai.yaml 2.3 KB
- references/agent_workflow_protocol.md 2.6 KB
- references/development_process_flow_protocol.md 18 KB
- references/distribution_release_protocol.md 3.0 KB
- references/failure_triage_protocol.md 2.7 KB
- references/plan_detailing_protocol.md 3.1 KB
- references/process_optimization_protocol.md 4.7 KB
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 · 50 lines · 20 tokens per session scan A 32ff88a31291
flowguard-development-process-flow is a skill published in the GitHub repository liuyingxuvka/FlowGuard (2 stars, last pushed 10d ago), licensed MIT. It adds 20 tokens to every session and 677 once invoked, about $0.0001 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 skills, from other repositories
documentation
Feature documentation and release notes patterns. Use when documenting changes, writing PR descriptions, or preparing releases.
release
Cut a new release: create the release branch (staging bake), then dispatch the production Release run on that branch.
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
release
Prepare, verify, and publish Sutando engine releases. Use when asked to prepare a release proposal, determine a version bump, audit release documentation, validate release gates, create a release PR, tag a confirmed release, or publish GitHub release notes. Preparation is safe and non-publishing; tagging and…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
repo-sentinel
Full security audit for public repositories across 12 attack surfaces: git history, secrets, CI/CD, containers, dependencies, licenses. Triggers on: "push to GitHub", "make repo public", "open source this", "is this safe to push", "release audit", "secret leaks".