agentmods.dev

agent-verdict-assessor

agent-verdict-assessor is an agent for Claude Code from transilienceai/communitytools. It costs 82 tokens per session (739 once invoked), scanned A, original, MIT.

A compliance decision-making role that assigns one status to each PCI SSS v2.0 test requirement: met, not met, partly met, not applicable, or needing human review. PCI SSS is a security standard for payment software.

In plain words
What is it for?
Use it to assess source-code and documentation evidence for payment-security requirements, check refuter feedback, and record a defensible status for each requirement.
Why use it?
It makes verdicts depend on cited evidence and independent attempts to disprove the conclusion. Unclear, unsupported, or disputed results are sent for manual review.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the communitytools plugin — 48 skills, 5 commands, 9 agents, 1 hook shipped together

not rated 520repo +8 1mo ago A scan 82 tokens original MIT

Good fit Use it to assess source-code and documentation evidence for payment-security requirements, check refuter feedback, and record a defensible status for each requirement.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/transilienceai/communitytools/verdict-assessor
View source ↗ transilienceai/communitytools transilience.ai
Install

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.

Clone the repo
git clone --depth 1 https://github.com/transilienceai/communitytools

Made for: Claude Code.

Or install communitytools, the plugin that ships this one along with the rest of its 48 skills, 5 commands, 9 agents, 1 hook.

Wrote 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.

agentmods badge for agent-verdict-assessor

README.md
[![agentmods](https://agentmods.dev/badge/agents/transilienceai/communitytools/verdict-assessor/github.svg)](https://agentmods.dev/agents/transilienceai/communitytools/verdict-assessor)
Your own site
<a href="https://agentmods.dev/agents/transilienceai/communitytools/verdict-assessor"><img src="https://agentmods.dev/badge/agents/transilienceai/communitytools/verdict-assessor/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.

agentmods 80×15 button for agent-verdict-assessor

Your own site · 80×15
<a href="https://agentmods.dev/agents/transilienceai/communitytools/verdict-assessor"><img src="https://agentmods.dev/badge/agents/transilienceai/communitytools/verdict-assessor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 739 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.00739
Opus 5 $0.00041 $0.00369
Sonnet 5 $0.00016 $0.00148
Haiku 4.5 $0.00008 $0.00074

Measured 10d ago against content hash 3859a2892c67, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

agent-verdict-assessor 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 10d 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.

skills/pci-secure-software/reference/agents/verdict-assessor.md · 39 lines

How it starts

The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent — verdict-assessor

Turns gathered evidence + adversarial votes into a recorded RequirementVerdict (schema.md §3). One per atomic Test Requirement.

Inputs

  • The Test Requirement (catalog row) and the gathered evidence package from findings/<id>/evidence/.
  • The proposed status from the assessor and the N blind refuter votes (refutation-validator).

The status rules

  • MET — the cited evidence satisfies the test requirement text AND refutations are below majority AND no refuter raised citation_doubt.
  • NOT_MET — the evidence shows the control is absent/insufficient (with the gap cited).
  • PARTIALLY_MET — some lettered sub-conditions are met and others are not, each with its own cited evidence.
  • NOT_APPLICABLE — the requirement's applicability predicate is false; carry the negative evidence.
  • REQUIRES_MANUAL_REVIEW — anything not honestly provable: dynamic-required-but-not-run, ambiguous evidence, or a downgrade (below).

Kill rules (apply strictly)

  1. A MET/NOT_MET stands only if its evidence is present AND refuted_count < floor(votes/2)+1 AND no refuter flagged citation_doubt. Otherwise downgrade to REQUIRES_MANUAL_REVIEW and set downgraded_from.
  2. A MET/NOT_MET with zero cited evidence → downgrade.
  3. dynamic_required_not_run → REQUIRES_MANUAL_REVIEW, regardless of anything else.
  4. NOT_APPLICABLE without negative evidence → REQUIRES_MANUAL_REVIEW.

Output discipline

  • Write the verdict JSON to artifacts/validated/<id>.json for a surviving status, OR to artifacts/false-positives/<id>.json when a proposed MET/NOT_MET was downgraded (the downgrade record is its sole home — a downgraded claim never appears as MET in the report).
  • Always set control_ref (framework:"PCI_SSS_v2.0", version:"2.0", the test_requirement_id/requirement_id/objective), why, and (for NOT_MET/PARTIALLY_MET) a remediation.
  • The deterministic citation verifier runs after you and will quarantine any verdict whose citations do not actually exist — do not pre-empt it by softening quotes.

Read the full file on GitHub · 39 lines

Changes

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.

  1. 10d ago First seen · 39 lines · 82 tokens per session scan A 3859a2892c67

Subscribe to this mod's changes

agent-verdict-assessor is an agent published in the GitHub repository transilienceai/communitytools (520 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 739 once invoked, about $0.0004 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.

ProductivitySecurityTestingbounty-huntershackeronepentestpentest-toolsecurity-research
Related

Other agents, from other repositories

auth-tester

Test authorization and access control across endpoints with ≥2 auth states. Returns IDOR / BFLA / auth-bypass findings.

TyrusRC/praetor · 30 tokens

command-expert

Create CLI commands for automation and tooling. Use PROACTIVELY when designing command-line interfaces, argument parsing, or task automation.

davepoon/buildwithclaude · 30 tokens

quality-fixer

Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.

shinpr/claude-code-workflows · 44 tokens

integration-test-reviewer

Reviews changed integration and E2E tests against skeletons, proof obligations, or explicit prompt claims. Use after test implementation or when test review/skeleton verification is requested. Returns only material proof gaps with the smallest sufficient corrections.

shinpr/claude-code-workflows · 50 tokens

developers

VP of Engineering who leads six skills — superpowers (engineering protocols), context7 (live library docs), mcp-builder (MCP servers), skill-creator (new skills), webapp-testing (browser QA), claude-mem (persistent memory). Use PROACTIVELY for any coding, debugging, testing, docs-lookup, MCP-server, skill-authoring or…

alebgl77/claude-inc · 124 tokens

js-analyst

Deep JavaScript analysis — secrets, DOM sinks, hidden API endpoints. Returns enriched JS intel for the orchestrator.

TyrusRC/praetor · 28 tokens