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 MSiccDev/ai-context-kitnpx agentmods add plugins/msiccdev/ai-context-kit/marketplacegit clone --depth 1 https://github.com/MSiccDev/ai-context-kitGrade A, and why
ai-context-kit 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 yesterday.
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": "ai-context-kit",
"description": "Context-aware AI collaboration skills for creating and validating user context, project AGENTS.md files, and skill artifacts across LLM providers.",
"owner": {
"name": "MSiccDev Software Development"
},
"plugins": [
{
"name": "ai-context-kit",
"source": {
"source": "github",
"repo": "MSiccDev/ai-context-kit"
},
"description": "Context-aware AI collaboration skills and implementation loop prompts for creating and validating user context, project AGENTS.md files, and skill artifacts across LLM providers.",
"version": "1.4.2",
"license": "MIT",
"homepage": "https://github.com/MSiccDev/ai-context-kit",
"repository": "https://github.com/MSiccDev/ai-context-kit",
"keywords": [
"context",
"agents",
"skills",
"user-context",
"ai-collaboration",
"prompt-engineering",
"implementation-loop",
"workflow-prompts"
]
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 32 lines scan A a181f98cdf84
ai-context-kit is a plugin published in the GitHub repository MSiccDev/ai-context-kit (12 stars, last pushed 4d 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
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.
memory-toolkit
Session memory lifecycle for developers — structured markdown memory, workstreams, handoff, auto-save hooks. No vector DB, no external dependencies.
memory-toolkit
Plugin marketplace listing 1 plugin: memory-toolkit.
claude-plugin
Connect Claude Code to Stash — stream activity to your Stash and collaborate with your other agents.
titen
Evidence-grounded collaborative memory for coding agents.