Borrowing it
Nothing to install: this file belongs to aget-framework/aget. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aget-framework/aget/main/.claude/skills/aget-check-facts/SKILL.mdgit clone --depth 1 https://github.com/aget-framework/agetWrote 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/aget-framework/aget/aget-check-facts)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-check-facts"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-check-facts/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/aget-framework/aget/aget-check-facts"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-check-facts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.01799 |
| Opus 5 | $0.00019 | $0.00899 |
| Sonnet 5 | $0.00008 | $0.00360 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
aget-check-facts 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- aget-check-facts — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-check-facts
Verify factual claims using a stratified 3-pass protocol. Operationalizes the conversational assertion provenance gap (L803) as structured verification.
Purpose
V-tests gate artifacts and ground-truth checks gate handoffs, but nothing gates mid-conversation factual claims. Unverified assertions propagate through a chain: conversation -> session record -> L-doc -> CLAUDE.md -> fleet-wide behavior. Cross-fleet evidence (4+ agents across 2+ fleets) independently identified this as a structural deficiency.
Evidence: L803 (Conversational Assertion Provenance Gap), L801 (Cross-Fleet False Positive — asserted "12/17 L-doc citations are fabricated" without verifying it was checking the wrong L-space), L756 (AGCI Verification Protocol), L802 (Convergent Architecture across 4+ agents), L807 (Incident Density = Urgency, 3x in one session), L782/remote (Stratified 3-pass discovery). CCB INTEL-002 (21 documented incidents).
Input
$ARGUMENTS
Parameters:
| Mode | Trigger | Scope |
|---|---|---|
| Self-check | /aget-check-facts (no args) |
Review own recent assertions in conversation |
| Targeted | /aget-check-facts [claim] |
Verify specific claim |
| Artifact | /aget-check-facts --file [path] |
Verify claims in a session file or L-doc |
Examples:
/aget-check-facts— Self-check recent conversation assertions/aget-check-facts the fleet has 34 agents— Verify specific claim/aget-check-facts --file sessions/SESSION_2026-04-10_1400.md— Verify claims in artifactcheck facts— Natural language triggerverify that— Alias for targeted check
Execution
Step 1: Identify Claims
Extract factual claims from the scope:
| Scope | Extraction Method |
|---|---|
| Self-check | Scan own recent conversation messages for entity names, dates, counts, identifiers, and causal assertions |
| Targeted | Parse the specific claim from $ARGUMENTS |
| Artifact | Read file, extract assertions containing names, dates, counts, identifiers |
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.
- 10d ago First seen · 153 lines · 38 tokens per session scan A 88e26e7f9023
aget-check-facts is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 1,799 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-08-30.
Other skills, from other repositories
aget-close-project
Close a PROJECTPLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECTPLAN…
aget-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual-mandate: spec coverage audit + deep bug finding.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818). Coverage and consistency mode.
aget-file-issue
File issues with L520 governance compliance.
aget-release-build
Execute gate deliverables with the Builder perspective of the Release Delivery Triad (L818). Speed-optimized execution mode.
aget-propose-actions
Propose ranked next-best actions with evidence grounding, time budgets, and execute-all default. Formalizes the fleet's highest-frequency interaction pattern.