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.
/plugin marketplace add oldskultxo/aictxnpx agentmods add plugins/oldskultxo/aictx/aictxgit clone --depth 1 https://github.com/oldskultxo/aictxWrote 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/plugins/oldskultxo/aictx/aictx)<a href="https://agentmods.dev/plugins/oldskultxo/aictx/aictx"><img src="https://agentmods.dev/badge/plugins/oldskultxo/aictx/aictx.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
aictx 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 3d 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.
What it actually says
{
"name": "aictx",
"description": "Use AICTX repo-local operational continuity in Claude Code.",
"version": "7.0.1",
"author": {
"name": "Santi Santamaria",
"url": "https://github.com/oldskultxo"
},
"homepage": "https://aictx.org",
"repository": "https://github.com/oldskultxo/aictx",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 48 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 13 lines scan A 1c5d838c7c2f
aictx is a plugin published in the GitHub repository oldskultxo/aictx (57 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
alive
Local, user-owned context for Claude Code. Keep your work in files you control.
claude-context-optimizer
Opus 4.8-aware context optimization: cache-aware real costs & cache-break detection, session baseline audit (/cco-overhead), auto .contextignore, self-calibrating estimates, delegation advisor, ru/en prompt coach, per-language token estimation, tunable thresholds via /cco-config, self-learning tool costs, team pattern.
scs-team
Structured Context for Teams - Initialize, build, validate, and version structured context from your PRDs, architecture docs, and compliance requirements. Compiles to Claude Code rules automatically.
scs-vibe
Structured Context for Vibe Coders - Stop Claude from coding you into corners. Quick, conversational setup that helps solo devs and small teams create architectural context in minutes.
video-to-llm
Read local video by turning it into one timestamped, citable document — once. Fully offline, resumable, built for hours of video.
llm-handoff
Cross-LLM context handoff — creates a complete handover.md so any LLM can continue your work without mistakes. Auto-triggers before context compaction.