Borrowing it
Nothing to install: this file belongs to liuyingxuvka/FlowGuard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/liuyingxuvka/FlowGuard/main/.agents/skills/flowguard-test-mesh/SKILL.mdgit 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-test-mesh)<a href="https://agentmods.dev/skills/liuyingxuvka/flowguard/flowguard-test-mesh"><img src="https://agentmods.dev/badge/skills/liuyingxuvka/flowguard/flowguard-test-mesh/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/liuyingxuvka/flowguard/flowguard-test-mesh"><img src="https://agentmods.dev/badge/skills/liuyingxuvka/flowguard/flowguard-test-mesh.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.00689 |
| Opus 5 | $0.00014 | $0.00345 |
| Sonnet 5 | $0.00006 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
flowguard-test-mesh 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 9d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FlowGuard Test Mesh
Purpose
Govern owners, results, freshness, path quality.
Entrypoint Scope
A standalone FlowGuard satellite skill; owner test_mesh_maintenance; structures evidence, not semantics/execution.
Local Material Routing
Read references/test_mesh_protocol.md; load references/test_mesh_reuse_protocol.md, references/test_mesh_long_check_protocol.md, references/test_mesh_release_protocol.md only when triggered.
Entrypoint Acceptance Map
Review a model-derived mesh, block incomplete evidence, and hand decisions to typed owners.
Use When
- Large/slow/background child test scripts, stale/reused evidence, release gates, parent/child test hierarchy, artifact-payload matrices, or diagnostic boundaries.
Do Not Use When
- Do not split code/models or choose semantics; send small tests to
flowguard.
Required Workflow
- Define the parent gate and derive child test scripts/suites from a validation-structure model.
- Freeze inventory; map each required surface, obligation, witness/check, member, case, shard to one owner.
- Attach status, freshness, artifacts, reuse, terminal id, fingerprints, coverage, counts, findings; provider context is not evidence.
- Bind long-check inputs/traces in
ProofArtifactRef.artifact_fingerprints; progress is liveness only. Return child evidence and handoffs.
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.
- PID/log/progress proves liveness; reuse needs current
TestResultReuseTicket/ProofArtifactRef. One receipt fans out only inside its boundary; copies are not executions. - Require
planned = executed + not_run,failed <= executed, no not-run underdeclared_complete, visible reasons, stable finding ids. - Local green cannot prove completeness. Every item is executed or delegated; delegation needs one owner and current evidence.
- Resolve owners before execution: missing/stale=
execute; exact-current pass=reuse_current; malformed/tampered/ambiguous/unknown-impact/in-flight=blocked. - Persist each successful child immediately; later requests execute only failed/stale owners and recompose exact identities.
- One parent invocation verifies each current child once, derives aggregates from one observation, performs one final source check, batch-publishes leaves, and reconciles ids once. Never persist the observation or repeat per-leaf semantics/currentness/store scans.
- TestMesh verifies cited evidence but cannot create necessity witnesses, select candidates, recompute Pareto dominance, or promote
normative_target. Deep members need current triggers.
What ships with it
8 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 29 KB
- .skillguard/compiled-contract.json 36 KB
- .skillguard/contract-source.json 10 KB
- agents/openai.yaml 1.4 KB
- references/test_mesh_long_check_protocol.md 1.2 KB
- references/test_mesh_protocol.md 7.8 KB
- references/test_mesh_release_protocol.md 1.2 KB
- references/test_mesh_reuse_protocol.md 2.0 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.
- 9d ago First seen · 44 lines · 28 tokens per session scan A 5207555bb143
flowguard-test-mesh is a skill published in the GitHub repository liuyingxuvka/FlowGuard (2 stars, last pushed 14d ago), licensed MIT. It adds 28 tokens to every session and 689 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
copilotkit-contribute
Use when contributing to the CopilotKit open-source project — forking, cloning, setting up the monorepo, creating branches, running tests, and submitting pull requests against CopilotKit/CopilotKit.
voice-agent-test-harness
Drive a fixed suite of spoken tests against a voice agent ("subject") from a co-located machine ("prober"), measure response latency / clarity / accuracy, diff against baseline, and report to the owner over Telegram.
test-harness
Generates pytest test suites with happy path, edge cases, error conditions, fixture scaffolding, mocks, async patterns. Triggers on: "generate tests", "write tests for", "test this function", "create test suite", "pytest for", "unit tests for", "mock strategy for".
surrogate-verifier
Generates structured test assertions and failure diagnostics for skill packages from a definition and task prompt. Triggers on: "verify this skill", "generate assertions", "surrogate verification", "diagnose skill failure". NOT for code review, use pr-review.
ship-workflow
Automated release pipeline: merges main, runs tests, pre-landing review, version bump, changelog, bisectable commits, and PR creation. Triggers on: "ship it", "release this", "prepare for release", "open a PR", "push and PR", "land this", "/ship-workflow".
Kafka Event-Driven Testing
Test Kafka-based event-driven systems, producer and consumer integration tests with Testcontainers, schema compatibility gates, idempotency and ordering verification, dead-letter handling, and end-to-end event flow assertions.