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 agentrust-io/integrations --skill agent-integritygit clone --depth 1 https://github.com/agentrust-io/integrationsWrote 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/agentrust-io/integrations/agent-integrity)<a href="https://agentmods.dev/skills/agentrust-io/integrations/agent-integrity"><img src="https://agentmods.dev/badge/skills/agentrust-io/integrations/agent-integrity/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/agentrust-io/integrations/agent-integrity"><img src="https://agentmods.dev/badge/skills/agentrust-io/integrations/agent-integrity.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.00033 | $0.00712 |
| Opus 5.5 | $0.00013 | $0.00285 |
| Sonnet 5.5 | $0.00007 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
agent-integrity 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgenTrust agent integrity
Use the capture engine shipped with this plugin. Resolve
../../engine/capture.py from this SKILL.md to an absolute path before
running it. Resolve ../../scripts/signing-python.py the same way.
The engine stores only names and hashes. Do not inspect auth.json, transcript
files, tool inputs, tool outputs, environment secrets, or raw configuration
values for this workflow.
Select the operation
- Verify is the default. Run it when the user asks whether the Codex agent changed, requests an integrity check, or names no operation.
- Snapshot shows the current fingerprints without comparing or changing the baseline.
- Approve replaces the baseline. Run it only when the user asked to establish, accept, approve, or rebaseline the current composition. A verification result alone does not authorize approval.
- Report creates signed Agent Manifest and TRACE records. The report does not alter the approved baseline.
Use the current working directory as the workspace unless the user names another one. The engine scopes baselines by a hash of the Git root, so checks in different repositories do not overwrite each other.
Run the engine
Use python3 on macOS or Linux and py -3 on Windows.
Verify:
python3 <engine-path> verify --cwd <workspace>
Snapshot:
python3 <engine-path> snapshot --cwd <workspace>
Approve after explicit user authorization:
python3 <engine-path> approve --cwd <workspace>
For a signed report, run the signing environment bootstrap with Python 3.11 or
newer. It creates a venv under $CODEX_HOME/agentrust/signing-venv and installs
the exact released versions from this plugin's requirements.txt. This is the
only step in the workflow that accesses PyPI.
python3 <signing-bootstrap-path>
<printed-python-path> <engine-path> report --cwd <workspace> --out <output-directory>
If the SessionStart hook did not capture the active model, add
--model <active-model-slug> only when the model slug is present in the
current Codex session. Never guess it.
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 · 89 lines · 33 tokens per session scan A dfab9b4b51b6
agent-integrity is a skill published in the GitHub repository agentrust-io/integrations (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 712 once invoked, about $0.0001 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.