Borrowing it
Nothing to install: this file belongs to sirkirby/unifi-mcp. 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/sirkirby/unifi-mcp/main/.agents/skills/mcp-response-redaction-governance/SKILL.mdgit clone --depth 1 https://github.com/sirkirby/unifi-mcpWrote 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/sirkirby/unifi-mcp/mcp-response-redaction-governance)<a href="https://agentmods.dev/skills/sirkirby/unifi-mcp/mcp-response-redaction-governance"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/mcp-response-redaction-governance/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/sirkirby/unifi-mcp/mcp-response-redaction-governance"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/mcp-response-redaction-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00215 | $0.03305 |
| Opus 5 | $0.00108 | $0.01653 |
| Sonnet 5 | $0.00043 | $0.00661 |
| Haiku 4.5 | $0.00021 | $0.00331 |
Grade A, and why
myco:mcp-response-redaction-governance 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Response Redaction Governance
This domain covers how sensitive-field disclosure (secrets, tokens, raw
credentials) is controlled across MCP tools and API responses. The
governing principle: request intent is not authorization. A caller
argument like include_sensitive=true expresses what the caller wants,
but only server/operator policy decides whether to honor it. Never let a
per-call argument directly gate secret disclosure.
Prerequisites
- Know which surface you're touching: an MCP product server
(
network/access/protect) or the REST API (api). Each surface has its own env-var prefix and resolves the redaction decision at a different point in the request lifecycle (see Procedure A). - Do not assume a single unified "PolicyEngine" class exists. Check
packages/unifi-core/src/unifi_core/policy.pyandpackages/unifi-core/src/unifi_core/policy_gate.pydirectly — there are two separate mechanisms, not one (see Procedure B). - Locate the correct enforcement point for what you're changing: read-path redaction and the mutation write-back guard are two different checks in two different files (see Procedure C). Don't assume one covers the other.
Procedure A: Configuring redaction policy per surface
Sensitive-field disclosure is controlled by a boolean, named for the enforced behavior rather than a data format:
policy:
response:
redact_sensitive_fields: true # default; true = redact secrets
Naming rationale: redact_sensitive_fields: true|false is clearer than
alternatives like sensitive_fields: redacted|raw, because the operator
is deciding whether the server redacts, not choosing an output format.
Keep this convention when adding new redaction toggles.
The boolean is resolved by should_redact_sensitive_fields(server_prefix, config, env) in packages/unifi-core/src/unifi_core/policy.py, in this
order (highest specificity wins):
UNIFI_{SURFACE}_REDACT_SENSITIVE_FIELDS— per-surface env override (e.g.UNIFI_NETWORK_REDACT_SENSITIVE_FIELDS,UNIFI_API_REDACT_SENSITIVE_FIELDS)UNIFI_REDACT_SENSITIVE_FIELDS— global env fallbackpolicy.response.redact_sensitive_fieldsfrom the surface's own config- Default:
true(redact) if nothing is set — safe-by-default
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 Changed · +17 lines c64e4d0879ac
- 13d ago First seen · 261 lines · 215 tokens per session scan A 26eb13a02da8
myco:mcp-response-redaction-governance is a skill published in the GitHub repository sirkirby/unifi-mcp (809 stars, last pushed yesterday), licensed MIT. It adds 215 tokens to every session and 3,305 once invoked, about $0.0011 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-30.
Other skills, from other repositories
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this…
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
frontmcp-development
Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents…
pipefy-api-fallback
Use this skill when an MCP tool fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow the 3-tier…