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 andregusman-raiz/a-gusman-claude --skill ag-sentinelgit clone --depth 1 https://github.com/andregusman-raiz/a-gusman-claudeWrote 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/andregusman-raiz/a-gusman-claude/ag-sentinel)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-sentinel"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-sentinel/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/andregusman-raiz/a-gusman-claude/ag-sentinel"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-sentinel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00044 | $0.00863 |
| Opus 5 | $0.00022 | $0.00432 |
| Sonnet 5 | $0.00009 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
ag-sentinel 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SENTINEL — Maquina Autonoma de Seguranca
Invocacao
/sentinel https://app.example.com # Producao (DEFENSIVE auto)
/sentinel ~/Claude/GitHub/raiz-platform # Local (OFFENSIVE auto)
/sentinel https://preview-xyz.vercel.app # Staging (HYBRID auto)
/sentinel ~/Claude/GitHub/fgts-platform --threshold 90
/sentinel https://app.example.com --audit-only
/sentinel --resume
/sentinel ~/Claude/GitHub/raiz-platform --mode defensive # Override modo
O que faz
Executa security + performance + compliance AUTONOMO em 5 fases:
- RECON — Mapeia superficie de ataque (endpoints, auth, headers, deps)
- SIEGE — Testa 6 dimensoes:
- S1-SHIELD: Headers, CORS, cookies, HTTPS
- S2-GATES: Auth bypass, session, RBAC
- S3-WALLS: Injection (SQL, XSS, CMD), validacao
- S4-VAULT: Secrets, .env, git history, deps
- S5-STRESS: Load test k6 (5-200 VUs)
- S6-GUARD: LGPD, PII, audit trail
- ARMOR — Hardening + fix de vulnerabilidades
- CONVERGE — Calcula SSS, loop ate >= threshold
- CERTIFY — Security Certificate, Load Report, Fix PR, issues
Modo Hybrid
| Ambiente | Modo | Payloads | Load Test |
|---|---|---|---|
| Producao | DEFENSIVE | Nenhum | Smoke (5 VUs) |
| Staging | HYBRID | Leves | Load (50 VUs) |
| Local | OFFENSIVE | Completos | Full (200 VUs) |
Execucao
Agent({
subagent_type: "ag-sentinel",
prompt: "{input do usuario}",
run_in_background: true,
mode: "auto"
})
Ferramentas Externas (opcionais)
| Ferramenta | Proposito | Install |
|---|---|---|
| k6 | Load testing | brew install k6 |
| trufflehog | Secrets em git | brew install trufflehog |
| semgrep | SAST analysis | pip3 install semgrep |
Se ausentes: degraded mode (grep manual) ou SKIP da dimensao.
Artefatos Produzidos
| Artefato | Arquivo |
|---|---|
| Security Certificate | docs/sentinel-certificate-YYYY-MM-DD.md |
| Load Test Report | docs/sentinel-load-report-YYYY-MM-DD.md |
| Fix PR | GitHub PR com hardening |
| Baselines | sentinel-baselines.json |
| State (recovery) | sentinel-state.json |
| KB Update | ~/.claude/shared/sentinel-kb/ |
| Issues backlog | GitHub Issues label sentinel-finding |
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 · 86 lines · 44 tokens per session scan A 7bff490f7382
ag-sentinel is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 863 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
compliance-audit
Audits codebases against compliance frameworks (SOC2, HIPAA, PCI-DSS, GDPR, ISO27001, etc.) using parallel agents per subdirectory/sub-repo. Produces a detailed markdown report with line-level code references. Use when you need to check a directory or monorepo for compliance violations before an audit or review.
stripe-dispute
Fight Stripe disputes and chargebacks by gathering evidence (Stripe API + your app database + terms page), generating an activity-log PDF, and submitting a counter-dispute. Use when the user says "fight dispute", "stripe dispute", "chargeback", "counter dispute", "dispute evidence", or shares a Stripe dispute ID.
legal-discovery
Audit e-discovery and litigation document review systems -- data collection pipelines (PST, MBOX, SharePoint, Slack), document processing (OCR via Tesseract/ABBYY, metadata extraction, deduplication), Technology Assisted Review (TAR 1.0/2.0/CAL with recall/precision tracking).
litigation-predictor
Audit litigation analytics and case outcome prediction systems -- ML outcome models (logistic regression, gradient boosting, neural nets with temporal train/test splits), settlement range modeling (Monte Carlo simulation, comparable case matching, BATNA analysis).
sales-readiness
Audit whether a product is ready for enterprise sales. Use when you need to assess SSO/SAML/SCIM support, RBAC maturity, multi-tenancy data isolation, audit logging coverage, public API quality, SLA operational readiness, SOC2/ISO27001 certification gaps, GDPR data residency controls.