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 aget-framework/template-advisor-aget --skill aget-check-factsgit clone --depth 1 https://github.com/aget-framework/template-advisor-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/template-advisor-aget/aget-check-facts)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-check-facts"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-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/template-advisor-aget/aget-check-facts"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-check-facts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.5 | $0.00015 | $0.00720 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to aget-check-facts — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo 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/template-advisor-aget (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,799 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to aget-check-facts, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
telegram
Telegram Bot skill for sending and editing Telegram messages via Bot API. Use when Bub needs to: (1) Send a message to a Telegram user/group/channel, (2) Reply to a specific Telegram message with replytomessageid, (3) Edit an existing Telegram message, or (4) Push proactive Telegram notifications. Prefer rich…
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
modern-python-toolchain
Modern Python project setup with uv, ruff, and pyright. Use when initializing a new Python project, configuring the Python environment, setting up linting/formatting, or when a project needs uv (the fast Python package manager). Trigger on: 'set up Python', 'new Python project', 'configure uv', 'install uv', 'ruff'…
vexor-cli
Semantic file discovery via vexor. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.
gap-analyzer
Compares a CLI's implemented commands against its APP.md API map and traffic-analysis.json to find missing endpoints, incomplete CRUD, dead client methods, and priority gaps. Runs as the mandatory first step of /cli-anything-web:refine and as an optional pre-review scan in standards.
linkedin-cli
Interacts with LinkedIn via the cli-web-linkedin command-line tool — search people/jobs/companies, view profiles and feed, create/edit/delete posts, react and comment, manage connections and invitations, read and send messages, view notifications, follow companies. Use when the user asks about LinkedIn or wants to…