Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Teamnpx agentmods add skills/aaaaqwq/agi-super-team/channel-truth-runWrote 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/aaaaqwq/agi-super-team/channel-truth-run)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/channel-truth-run"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/channel-truth-run/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/aaaaqwq/agi-super-team/channel-truth-run"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/channel-truth-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 114 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 114 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 121 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 122 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 122 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00010 | $0.01111 |
| Opus 5 | $0.00005 | $0.00556 |
| Sonnet 5 | $0.00002 | $0.00222 |
| Haiku 4.5 | $0.00001 | $0.00111 |
Grade A, and why
channel-truth-run 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channel Truth Run
Runs the Channel Truth Agent to synchronize last_contact timestamps
When to use
- "run channel truth"
- "update last contact dates"
- "synchronize contact dates"
- "run channel truth agent"
What it does
Channel Truth Agent:
- Loads all activities from
activities.csv - Finds the most recent communication for each contact
- (Optionally) Scans channels (Email, Telegram, WhatsApp, LinkedIn)
- Merges data and resolves conflicts
- Updates
people.csv,leads.csv,clients.csvwith current dates - Generates a report (stale/hot contacts)
- Sends summary to Telegram
How to execute
Run modes
# Full run (default)
cd $AGENTS_PATH/channel-truth
python3 channel_truth_agent.py
# Dry-run (read only, no writes)
python3 channel_truth_agent.py --dry-run
# Single contact (for debugging)
python3 channel_truth_agent.py --person-id=p-acme-001
# Without channel scanning (activities.csv only)
python3 channel_truth_agent.py --no-channels
Pre-run checks
# Check if activities.csv exists
ls -lh $CRM_PATH/activities.csv
# Check people.csv
ls -lh $CRM_PATH/contacts/people.csv
# Dry-run test
python3 channel_truth_agent.py --dry-run
After run
# View report
ls -lt $AGENTS_PATH/reports/channel_truth_*.md | head -1
# View latest report
cat $(ls -t $AGENTS_PATH/reports/channel_truth_*.md | head -1)
# View logs
tail -20 $AGENTS_PATH/logs/channel_truth.json
Output
-
Updated CSV files:
people.csv- addedlast_contactandlast_updatedleads.csv- addedlast_contact_via_primaryclients.csv- addedlast_contact_via_primary
-
Report:
$AGENTS_PATH/reports/channel_truth_YYYY-MM-DD.md
-
Backup files:
people.csv.bak.TIMESTAMPleads.csv.bak.TIMESTAMPclients.csv.bak.TIMESTAMP
-
Telegram notification:
- Summary: how many updated, hot/stale contacts
Rollback
If something went wrong:
# Rollback via backup
cd $CRM_PATH/contacts/
ls -lt people.csv.bak.* | head -1
cp people.csv.bak.YYYYMMDD_HHMMSS people.csv
cd ../relationships/
cp leads.csv.bak.YYYYMMDD_HHMMSS leads.csv
cp clients.csv.bak.YYYYMMDD_HHMMSS clients.csv
# Or via git
cd $PROJECT_ROOT
git log --oneline sales/crm/
git revert <commit-hash>
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.
- 6d ago First seen · 182 lines · 10 tokens per session scan A a8a3768dd8a2
channel-truth-run is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (91 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 1,111 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
dos-goal-fleet
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.
flo
MoFlo ticket spell - analyze and execute GitHub issues.
dos-next-up
Snapshot the repo's phased-plan portfolio into a dispatch packet: audit candidates with dos verify, render who-does-what, and emit a dos gate verdict. Use when you need the current next-work view before dispatching agents.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.