Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

aivss-gate

Estrelas3

Forks1

Atualizado27 de junho de 2026 às 10:37

Show per-critic AIVSS gate config, per-agent model assignments (HarnessModelGuardian), and last SIEM event summary. Use to verify gate thresholds are set, check which agents have custom models configured, and inspect the most recent inbound/internal/outbound scores. Read-only — no side effects.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

BerdTan

BerdTan/threatassessor

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	aivss-gate
description	Show per-critic AIVSS gate config, per-agent model assignments (HarnessModelGuardian), and last SIEM event summary. Use to verify gate thresholds are set, check which agents have custom models configured, and inspect the most recent inbound/internal/outbound scores. Read-only — no side effects.
allowed-tools	Bash(python3:) Bash(source:)

AIVSS Gate Inspector

Prints three sections in sequence: the per-critic gate table, the per-agent model config, and the last SIEM event. No API calls, no file writes.

Run

cd "$(git rev-parse --show-toplevel)" && source .venv/bin/activate && python3 .claude/skills/aivss-gate/scripts/aivss-gate.py

What it shows

Section	What you see
Per-Critic Gate Config	Critic name, allowed models, allowed tools, AIVSS gate threshold (10.0 = disabled; lower = active)
Per-Agent Model Config	Each swarm agent, its configured primary model + fallbacks, or "env-var default" if not set
Last SIEM Event	Architecture, timestamp, run_id, inbound/internal/outbound composites, overall severity, top threat, governance dim severities D1–D5

Failure fixes

Error	Fix
`settings` import fails	Ensure `.venv` is activated; run `/quick-test` to verify deps
`No SIEM log found`	No pipeline run yet, or `governance.save_signals_per_run` is False in settings
Gate threshold shows 10.0 for all critics	No per-critic gate configured — add a `critics` block to `chatbot/config/user_config.json`
Per-agent models all show "env-var default"	No `agent_models` block in `user_config.json` — configure via Harness tab → Harness Config

When to use

After a pipeline run to confirm governance signals were scored
When diagnosing "why did critic X get blocked?" — check gate threshold vs last inbound score
To verify HarnessModelGuardian is routing the right models to each agent
Before a demo — confirm AIVSS and model config is as expected

Related skills

/aivss-score — recompute AIVSS scores fresh from a report directory
/backfill-aivss — generate governance_signals.json for all past reports missing it
/quick-test — broader integration sanity check

Mais deste repositório

mesmo repositório

rerun-corpus

BerdTan/threatassessor

Audit and selectively re-run the deterministic analysis engine across all 26 corpus architectures. Default (no args) shows a staleness check — which reports are missing metadata, which arch types need engine fixes re-applied, and the current corpus score table. Pass --ai-only to re-run only AI/agentic architectures, --all to re-run everything, or a single arch name to re-run one. Use after engine changes (self_validation.py, ground_truth_generator.py, rapids_driven_controls.py) to confirm scores are consistent and no regressions landed.

2026-07-123

tatb-score

BerdTan/threatassessor

Run TATB (TA Test Benchmark) on a single architecture and print the four-rubric scorecard — Threat-Relevant, TTP-Accurate, Risk-Defensible, Plan-Actionable. Uses the same scoring logic as the dashboard TATB tab. Pass an architecture name as argument, or omit for the most recent report. Read-only. ~3 seconds (includes MITRE API fetch).

2026-07-123

tatb-corpus

BerdTan/threatassessor

Score all architectures in /report/ across the four TATB rubrics and print a visual corpus map — bar table, heatmap, and pipeline stage attribution. Shows which architectures are Excellent/Solid/Weak/Draft on each dimension and identifies which pipeline stages to fix for the largest corpus-wide gain. No UI needed. ~10-15 seconds (MITRE fetch batched once).

2026-07-113

run-er

BerdTan/threatassessor

Run Expert Review (MoE critics + ScrumMaster) on any architecture that has an existing analysis. Three modes — sequential (3 core critics), full_moe (5 critics + SM, generates Plan-Actionable data), or single-critic (re-run one critic by name). Streams live critic results with scores, gaps, and final confidence. ~60–120s for full_moe, ~30–60s for sequential.

2026-07-113

tatb-loop

BerdTan/threatassessor

TATB feedback loop — observe corpus or single-arch TATB scores, diagnose weak signals, propose targeted pipeline stage fixes, gate on human approval, apply changes, re-run TATB to verify improvement, and log the before/after delta to docs/DECISIONS.md. The agent does NOT autonomously commit code; every code change requires explicit human approval.

2026-07-043

quick-test

BerdTan/threatassessor

Runs a fast ~15 second integration sanity check — verifies dependencies, rate limiter, MITRE data load (≥835 techniques), OpenRouter API key, API connection, and one real embedding call. Use at session start or after installing dependencies to confirm everything is working before coding.

2026-07-023

name	aivss-gate
description	Show per-critic AIVSS gate config, per-agent model assignments (HarnessModelGuardian), and last SIEM event summary. Use to verify gate thresholds are set, check which agents have custom models configured, and inspect the most recent inbound/internal/outbound scores. Read-only — no side effects.
allowed-tools	Bash(python3:) Bash(source:)

AIVSS Gate Inspector

Prints three sections in sequence: the per-critic gate table, the per-agent model config, and the last SIEM event. No API calls, no file writes.

Run

cd "$(git rev-parse --show-toplevel)" && source .venv/bin/activate && python3 .claude/skills/aivss-gate/scripts/aivss-gate.py

What it shows

Section	What you see
Per-Critic Gate Config	Critic name, allowed models, allowed tools, AIVSS gate threshold (10.0 = disabled; lower = active)
Per-Agent Model Config	Each swarm agent, its configured primary model + fallbacks, or "env-var default" if not set
Last SIEM Event	Architecture, timestamp, run_id, inbound/internal/outbound composites, overall severity, top threat, governance dim severities D1–D5

Failure fixes

Error	Fix
`settings` import fails	Ensure `.venv` is activated; run `/quick-test` to verify deps
`No SIEM log found`	No pipeline run yet, or `governance.save_signals_per_run` is False in settings
Gate threshold shows 10.0 for all critics	No per-critic gate configured — add a `critics` block to `chatbot/config/user_config.json`
Per-agent models all show "env-var default"	No `agent_models` block in `user_config.json` — configure via Harness tab → Harness Config

When to use

After a pipeline run to confirm governance signals were scored
When diagnosing "why did critic X get blocked?" — check gate threshold vs last inbound score
To verify HarnessModelGuardian is routing the right models to each agent
Before a demo — confirm AIVSS and model config is as expected

Related skills

/aivss-score — recompute AIVSS scores fresh from a report directory
/backfill-aivss — generate governance_signals.json for all past reports missing it
/quick-test — broader integration sanity check