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 ankitkr3/compounded --skill compounded-trust-trackergit clone --depth 1 https://github.com/ankitkr3/compoundedWrote 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/ankitkr3/compounded/compounded-trust-tracker)<a href="https://agentmods.dev/skills/ankitkr3/compounded/compounded-trust-tracker"><img src="https://agentmods.dev/badge/skills/ankitkr3/compounded/compounded-trust-tracker/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/ankitkr3/compounded/compounded-trust-tracker"><img src="https://agentmods.dev/badge/skills/ankitkr3/compounded/compounded-trust-tracker.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.00079 | $0.01046 |
| Opus 5.5 | $0.00032 | $0.00418 |
| Sonnet 5.5 | $0.00016 | $0.00209 |
| Haiku 4.5 | $0.00008 | $0.00105 |
Grade A, and why
compounded-trust-tracker 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trust Tracker (compounded)
compounded skills earn the right to act through demonstrated reliability. Your job is to apply the right level of caution at each trust state, and to honestly report outcomes so the gradient stays calibrated.
The four states, in detail
.proposed — untrusted, not in your skill index
Proposed skills are not loaded. You cannot invoke them. They exist only as candidates awaiting verification. Do not attempt to read or apply them. If the user asks you to use a proposed skill, explain that it has not been verified yet and offer to run /compounded:verify <skill> manually.
.verified — invoked by name only
A verified skill has passed exactly one replay verification. Treat it as a credible procedure but not yet a habit.
- Activation: only when the user names it explicitly, or when you decide a verified skill is clearly relevant and you announce its use.
- Confirmation: announce that you are loading the skill before applying it. e.g. "I'm going to use the
express-to-fastifyskill for this — it was verified once before." - Outcome reporting: if the skill works cleanly, compounded's logging will count this toward promotion to
.trusted. If the user corrects you, the skill demotes back to.proposed. Do not edit the trust state yourself; just report the outcome accurately.
.trusted — auto-loads, asks before applying
A trusted skill has been used successfully 3+ times without correction. It is known to work in this user's context.
- Activation: auto-load when the task description matches the skill's "When to use" section.
- Confirmation: ask before applying. e.g. "This task matches the
express-to-fastifytrusted skill. Should I use it?" - Skip confirmation only if the user has explicitly told you to apply trusted skills automatically in the current session.
.autonomous — runs without asking, every time
An autonomous skill has 10+ uses, with zero corrections in the last 5. It has earned full autonomy.
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 · 69 lines · 79 tokens per session scan A f4784d96413f
compounded-trust-tracker is a skill published in the GitHub repository ankitkr3/compounded (5 stars, last pushed 3mo ago), licensed MIT. It adds 79 tokens to every session and 1,046 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
access
Manage who may drive telegram-topics sessions — view and edit the user allowlist. Use when the user asks to allow or remove a Telegram user, check who's allowed, or lock the channel down.
version-sentinel
Use when adding, bumping, or changing a dependency in package.json, requirements.txt, constraints.txt, pyproject.toml, Cargo.toml, .csproj, .fsproj, or .vbproj. Triggered automatically by version-sentinel's PreToolUse hook (where the host supports hooks) — this skill explains how to satisfy the block and record a…
personal-voice-capture
Use when a user wants an agent to learn, encode, or improve their personal writing voice as a reusable skill through source-text ingestion and iterative calibration edits.
ai-trend-tracker
Answers questions about AI/ML news, tool launches, research papers, and learning resources (free courses, certificates, YouTube channels, podcasts, newsletters, learning paths) by searching the live web first and returning a cited, dual-layer (ELI5 + technical + honest verdict) explanation tailored to the user's role…
ai-native-design
A workflow for turning a product brief and API contract into frontend design prompts and implementation guidance. It supports three outside design channels and keeps generated frontend work aligned with the same brief and contract.
backend-development
A set of instructions for building server-side code such as APIs and database-backed applications. It uses API contracts, data models, the chosen technology stack, and tests as the project’s reference points.