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/ktcrisis/flux7-mesh/setupnpx skills add KTCrisis/flux7-mesh --skill setupgit clone --depth 1 https://github.com/KTCrisis/flux7-meshWrote 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/ktcrisis/flux7-mesh/setup)<a href="https://agentmods.dev/skills/ktcrisis/flux7-mesh/setup"><img src="https://agentmods.dev/badge/skills/ktcrisis/flux7-mesh/setup.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 | $0.00013 | $0.00518 |
| Opus 5 | $0.00006 | $0.00259 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade B, and why
setup scanned grade B with 1 finding 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 4d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- tools: ["*"] What it actually says
Generate a starter flux7-mesh configuration.
Templates available:
minimal(default) — single agent, basic allow/denytravel— travel agent with weather, flights, gmaildev— dev agent with filesystem, git, github
If $0 is "travel":
port: 9091
mcp_servers:
- name: weather
transport: stdio
command: npx
args: ["-y", "open-meteo-mcp-server"]
- name: flights
transport: stdio
command: npx
args: ["-y", "google-flights-mcp-server"]
policies:
- name: travel-agent
agent: "claude"
rules:
- tools: ["weather.*"]
action: allow
- tools: ["flights.*"]
action: allow
- name: default
agent: "*"
rules:
- tools: ["*"]
action: deny
If $0 is "dev":
port: 9090
mcp_servers:
- name: filesystem
transport: stdio
command: npx
args: ["-y", "@modelcontextprotocol/server-filesystem", "."]
policies:
- name: dev-agent
agent: "claude"
rules:
- tools: ["filesystem.read_file", "filesystem.list_directory"]
action: allow
- tools: ["filesystem.write_file"]
action: allow
condition:
field: "params.path"
operator: "not_contains"
value: ".env"
- name: default
agent: "*"
rules:
- tools: ["*"]
action: deny
Otherwise (minimal):
port: 9090
policies:
- name: my-agent
agent: "claude"
rules:
- tools: ["*"]
action: allow
- name: default
agent: "*"
rules:
- tools: ["*"]
action: deny
Write the config to config.yaml in the current directory. Confirm the file was written.
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.
- 4d ago First seen · 93 lines · 13 tokens per session scan B f6a2a64d2c06
setup is a skill published in the GitHub repository KTCrisis/flux7-mesh (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
achieving-cmmc-level-2-compliance
Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…
python-code-reviewer
Review Python OpenInference instrumentation code for correctness and completeness. Use this skill when reviewing a Python instrumentor package — whether it's a new instrumentor, a PR that modifies one, or when the user asks to audit/review/check an existing instrumentor's code quality. Trigger on phrases like "review…
genai-conformance
Run, interpret, and iterate on the OpenInference GenAI conformance MVP at python/openinference-instrumentation/scripts/conformance/. Use when the user mentions GenAI conformance, OTel GenAI semantic conventions, Weaver registry live-check, the dual-write conversion (genaiconversion.py, enablegenaisemconv), genai.…
opentelemetry-net-instrumentation
Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.
python-canary-fix
Investigate and propose fixes for Python canary cron failures in the openinference repo. Use when the user mentions Python canary failures, Python cron failures, or when the auto-fix CI job reports Python instrumentation canary issues.
escalation-governance
Assess whether to escalate models. Use when evaluating reasoning depth.