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.
git clone --depth 1 https://github.com/boykush/scrapsWrote 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/boykush/scraps/llm-wiki)<a href="https://agentmods.dev/plugins/boykush/scraps/llm-wiki"><img src="https://agentmods.dev/badge/plugins/boykush/scraps/llm-wiki/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/plugins/boykush/scraps/llm-wiki"><img src="https://agentmods.dev/badge/plugins/boykush/scraps/llm-wiki.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
llm-wiki 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 4d 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": "llm-wiki",
"version": "0.2.3",
"description": "Official Scraps LLM Wiki bundle. Skills and agents for ingesting sources, querying the wiki, applying the default Scraps LLM Wiki schema, and running purpose-driven lint via the scraps CLI.",
"author": {
"name": "boykush",
"email": "[email protected]"
},
"homepage": "https://boykush.github.io/scraps",
"repository": "https://github.com/boykush/scraps"
}
What it installs
The manifest is a name and a version. 2 skills, 2 agents travel with it, and installing the plugin installs all of them — 254 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.
- 4d ago Changed 45e65b34182c
- 5d ago Changed e3765c763734
- 1mo ago First seen · 12 lines scan A 5e6a3947c5c2
llm-wiki is a plugin published in the GitHub repository boykush/scraps (45 stars, last pushed today), 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
estelle
Estelle — code memory + the grounding gate, always on. The trust layer under your AI coding agents: it grounds every model in your real codebase and refuses to ship what isn't true.
simplicio-loop
Autonomous looping orchestrator + satellite skills that drains a backlog end-to-end on any LLM/runtime: discover, implement, verify, review, merge, close. /simplicio-loop is the unified public entrypoint for core + hardened loop; /simplicio-tasks remains only a legacy alias. Its Claude lifecycle route is Mapper-only…
simplicio-prompt
Tuple-Space + Yool safe-speed runtime for Claude Code. A UserPromptSubmit hook makes it always-on (injects the runtime contract on every prompt unless the user stands down). Routes any user input through a Hilbert-indexed tuple graph with lazy batchspawn, LaneWorkerPool, receipt cache, jittered backoff, circuit breake.
kin
Kin keeps a living map of the software itself so humans and agents can understand what every change touches. Locate, search, context packs, data-flow tracing, and impact analysis without raw file search.
quality
Code quality skills — refactoring, naming conventions, and project structure.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.