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 skills add fakoli/fakoli-plugins --skill gws-modelarmor-sanitize-responsegit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/gws-modelarmor-sanitize-response)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/gws-modelarmor-sanitize-response"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/gws-modelarmor-sanitize-response/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/fakoli/fakoli-plugins/gws-modelarmor-sanitize-response"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/gws-modelarmor-sanitize-response.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.00023 | $0.00290 |
| Opus 5 | $0.00012 | $0.00145 |
| Sonnet 5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
gws-modelarmor-sanitize-response 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 6d 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.
This is a copy
88% identical to gws-modelarmor-sanitize-response — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
modelarmor +sanitize-response
Reference: See the
gws-sharedskill for auth, global flags, and security rules.
Sanitize a model response through a Model Armor template
Usage
gws modelarmor +sanitize-response --template <NAME>
Flags
| Flag | Required | Default | Description |
|---|---|---|---|
--template |
✓ | — | Full template resource name (projects/PROJECT/locations/LOCATION/templates/TEMPLATE) |
--text |
— | — | Text content to sanitize |
--json |
— | — | Full JSON request body (overrides --text) |
Examples
gws modelarmor +sanitize-response --template projects/P/locations/L/templates/T --text 'model output'
model_cmd | gws modelarmor +sanitize-response --template ...
Tips
- Use for outbound safety (model -> user).
- For inbound safety (user -> model), use +sanitize-prompt.
See Also
- gws-shared — Global flags and auth
- gws-modelarmor — All filter user-generated content for safety commands
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.
- 6d ago First seen · 42 lines · 23 tokens per session scan A f394fa22bf11
gws-modelarmor-sanitize-response is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 290 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to gws-modelarmor-sanitize-response, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
audit
Read-only quality gate that audits already-built work against its stated requirement and Definition of Done before it is allowed to move to 2done/. Produces a severity-ranked decision proposal (BLOCKER/MAJOR/MINOR/NIT) with evidence, never a fix. Use when an item is claimed complete, before moving anything to 2done/…
pr-vetting
Use when the user wants to thoroughly investigate, vet, review, or security-scan a pull request before deciding how to handle it - especially PRs from external or unknown contributors. Runs a parallel multi-agent investigation (technical, security, value/fit, contributor reputation) and merges the findings into one…
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…
requirements-verbatim
Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decision that later work…
diag
Read-only root-cause diagnosis for a symptom, bug, failure, or unexpected behavior. Establishes the mechanism at file:line and reads up the facts instead of guessing, before any fix is attempted. Produces a diagnosis report; the fix is always a separate step gated by an explicit GO. Use when something is broken…
orchestration
Delegate work to subagents safely and efficiently - decide how many subagents to run, keep parallel tracks on disjoint files, monitor them without flooding your context, inherit security to every subagent, and use return-and-resume so a subagent can ask a question and continue with full context. Use whenever you are…