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-code-structure-recommendationnpx skills add liuyingxuvka/FlowGuard --skill flowguard-code-structure-recommendationgit 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-code-structure-recommendation)<a href="https://agentmods.dev/skills/liuyingxuvka/flowguard/flowguard-code-structure-recommendation"><img src="https://agentmods.dev/badge/skills/liuyingxuvka/flowguard/flowguard-code-structure-recommendation.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.00039 | $0.00615 |
| Opus 5 | $0.00019 | $0.00308 |
| Sonnet 5 | $0.00008 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
flowguard-code-structure-recommendation 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FlowGuard Code Structure Recommendation
Purpose
Derive recommendation-only FunctionBlock-to-module ownership, facades, adapters, fields, effects, and validation boundaries from a named model.
Entrypoint Scope
This standalone FlowGuard satellite skill owns code_structure_recommendation (public_owner), not refactoring.
Local Material Routing
After admission, read references/code_structure_recommendation_protocol.md for the complete schema and handoffs.
Entrypoint Acceptance Map
Accept a named current model; derive owners and boundaries; block omissions/duplicates; send existing-code work to StructureMesh.
Use When
- Use before code when module, function, facade, adapter, field/effect owner, or validation boundary is unclear.
Do Not Use When
- Do not refactor existing code, invent behavior, or replace parity evidence; return missing models to
flowguard.
Required Workflow
- Freeze the model, maturation/admission identities, blocks, state, fields, effects, and public entrypoints.
- Recommend cohesive modules, single owners, facades/adapters, and observable leaves; record StructureMesh, Model-Test Alignment, or FieldLifecycleMesh handoffs.
- For an explicit blueprint claim, fingerprint the exact model-element universe, disposition every required element, and emit reverse implementation-coverage obligations for the independent source audit.
- Without exact current admission for the same task/model/scope, remain recommendation-only.
Hard Gates
- Model-purpose gate: freeze task-specific failure(s); 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 the real FlowGuard check engine and AGENTS.md managed record; forbid a fake mini-framework.
- Do not invent modules before responsibilities. Every write needs one owner; public facades and validation boundaries stay explicit; oversized leaves split or remain scoped.
- A diagram or nonempty map is not readiness. Omitted elements, missing reverse obligations, fingerprint drift, or scope beyond admission block blueprint use. This route neither scans source nor proves static closure.
- Route ArchitectureReduction only for a concrete evidence-backed contraction candidate. Any model/maturation/admission identity drift makes this recommendation stale.
- Blueprint traceability targets, depth/first gap, explicit whole scope, affected-only default, no owner fallback, and separate decision axes follow the protocol.
What ships with it
5 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.
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 · 42 lines · 39 tokens per session scan A 7ae7c1521937
flowguard-code-structure-recommendation is a skill published in the GitHub repository liuyingxuvka/FlowGuard (2 stars, last pushed 10d ago), licensed MIT. It adds 39 tokens to every session and 615 once invoked, about $0.0002 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
backend-idempotency
Use this skill when the user says 'idempotency', 'idempotent', 'idempotency key', 'exactly-once', 'retry safety', 'deduplication', 'duplicate detection', 'idempotent endpoint', 'safe retry'. This skill implements idempotency keys and exactly-once semantics so retries never result in duplicate side effects. Applies to…
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
metrics-instrumentation
Specification for instrumenting an opik-backend workflow with operational OpenTelemetry metrics — per-stage throughput/latency/error counters and native histograms, dimensioned per-customer (workspace). Use when a pipeline (scoring, ingestion, experiments, jobs) needs per-stage visibility. Covers metric emission only…
review-agents-md
Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.
notifications
Send notifications through the unified notification router.
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.