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 Threat-Vector-Security/guardian-agent --skill security-alert-hygienegit clone --depth 1 https://github.com/Threat-Vector-Security/guardian-agentWrote 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/threat-vector-security/guardian-agent/security-alert-hygiene)<a href="https://agentmods.dev/skills/threat-vector-security/guardian-agent/security-alert-hygiene"><img src="https://agentmods.dev/badge/skills/threat-vector-security/guardian-agent/security-alert-hygiene/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/threat-vector-security/guardian-agent/security-alert-hygiene"><img src="https://agentmods.dev/badge/skills/threat-vector-security/guardian-agent/security-alert-hygiene.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.00000 | $0.00286 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
security-alert-hygiene 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.
What it actually says
Security Alert Hygiene
Use this when the main job is to manage alert state cleanly: acknowledge, resolve, suppress, or reduce duplicate noise.
Workflow
- Search first with
security_alert_search. - Narrow by source, type, and evidence pattern before mutating state.
- Choose the correct disposition:
security_alert_ackfor understood alerts that should remain visiblesecurity_alert_resolvefor investigated alerts that are closedsecurity_alert_suppressfor expected repetitive noise with an expiry
- Always record the operator reason when resolving or suppressing.
Decision Rules
- Use acknowledge when the alert is real and still relevant.
- Use resolve when the condition has been investigated and closed.
- Use suppress when the alert is expected to recur and would otherwise overwhelm the queue.
- Prefer suppressing one narrow pattern over broad source-wide suppression.
Boundaries
- Use
host-firewall-defenseornative-av-managementif the first problem is understanding whether the alert is meaningful. - Use
security-triageif multiple alert families suggest a broader incident.
Gotchas
- Do not suppress without an expiry unless there is a compelling operational reason.
- Do not resolve an alert just because it is noisy.
- Do not mutate alert state from a vague natural-language description when the exact alert id or narrow pattern can be found first.
What ships with it
1 file 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.
- 9d ago First seen · 32 lines · 0 tokens per session scan A de7c11efaa4d
security-alert-hygiene is a skill published in the GitHub repository Threat-Vector-Security/guardian-agent (13 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 286 tokens. 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
analyzing-powershell-script-block-logging
Parse Windows PowerShell Script Block Logs (Event ID 4104) from EVTX files to detect obfuscated commands, encoded payloads, and living-off-the-land techniques. Uses python-evtx to extract and reconstruct multi-block scripts, applies entropy analysis and pattern matching for Base64-encoded commands, Invoke-Expression…
agent-squad-typescript
Use when building or modifying a Node.js / TypeScript app that uses the agent-squad npm package — multi-agent orchestration: orchestrator, agents (all built-in types + GroundedAgent), classifier routing (Bedrock / Anthropic / OpenAI), storage (in-memory / DynamoDB / SQL), retrievers (Amazon KB / Dakera), and tools…
intent-recognition
Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embedsother (whether the other primitive appears embedded inside — an agent step inside a workflow, or a workflow invoked as an…
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
data-table-manager
Load before calling data-tables or parse-file. Use for natural standalone requests like "what data tables do I have?", "show/list my tables", or "what columns are in this table?", and whenever the user asks to list, show, create, inspect, import, seed, query, update, clean up, rename columns in, or delete data tables…
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.