Skip to content
Back to skills

Subagent Evidence

ASecurity

Dispatch-time contract for explore agents: return only observations each with a `file:line` citation and raw excerpt; inference must be explicitly tagged `[INFERRED]`. Post-dispatch, I sample-cite — verify ≥2 citations per summary myself before trusting conclusions.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 27, 2026
developmentrustshell

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add RMAzrim/opencode-artes --skill subagent-evidence --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Subagent Evidence?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Subagent Evidence
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rmazrim-subagent-evidence/badge)](https://www.skillsdirectory.com/skills/rmazrim-subagent-evidence)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Subagent Evidence
description: "Dispatch-time contract for explore agents: return only observations each with a `file:line` citation and raw excerpt; inference must be explicitly tagged `[INFERRED]`. Post-dispatch, I sample-cite — verify ≥2 citations per summary myself before trusting conclusions."
metadata:
  source: skills/subagent-evidence/subagent-evidence.md
---

# Subagent Evidence

## Prerequisites & Dependencies

- Access to explore agent dispatch workflow
- Power to post-process agent summaries before acceptance
- No external runtime dependencies

## Dispatch-Time Contract

When dispatching an explore agent, enforce the following contract:

1. **Observation-only return**: The agent returns raw observations, never inferred conclusions.

2. **Each observation must include**:
   - `file:line` citation — exact file path and line number where the observation originates
   - `excerpt` — the raw text snippet (1-3 sentences) from that location
   - `tag` — one of: `[OBSERVED]`, `[INFERRED]`, `[HEURISTIC]`

3. **Inference tagging requirement**: Any conclusion drawn by the agent must be explicitly tagged `[INFERRED]` and accompanied by at least 2 supporting observations with `file:line` citations.

4. **No bare claims**: Statements without `file:line` citations are rejected at dispatch time.

## Post-Dispatch Verification

After receiving an agent summary:

1. **Sample-cite**: For each substantive claim in the summary, locate and verify at least 2 `file:line` citations from the original observations.

2. **Flag unsupported conclusions**: Claims with fewer than 2 verified citations are marked `[UNVERIFIED]` in the chat.

3. **Reject inference without evidence**: Any `[INFERRED]` claim without 2 supporting observations is discarded and re-reported to the user.

## Verification Workflow Example

```
Agent summary: "The codebase uses Factory pattern extensively"
→ I verify: 2+ citations showing Factory pattern usage
→ Result: Claim accepted with [VERIFIED] tag

Agent summary: "Component X is unused"
→ I check: only 1 citation found for "unused"
→ Result: Claim marked [UNVERIFIED], re-reported to user
```

## Windows PowerShell Notes

- Citation format: `C:\path\to\file.py:42` or relative paths as appropriate
- Excerpt extraction: use `sed -n '42p' "C:\path\to\file.py"` to pull exact line
- Tag markup: wrap inferences in `[INFERRED]` brackets explicitly in the summary text

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.