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/berabuddies/SemiaWrote 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/berabuddies/semia/claude-code)<a href="https://agentmods.dev/plugins/berabuddies/semia/claude-code"><img src="https://agentmods.dev/badge/plugins/berabuddies/semia/claude-code/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/berabuddies/semia/claude-code"><img src="https://agentmods.dev/badge/plugins/berabuddies/semia/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
semia 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.
What it actually says
{
"name": "semia",
"version": "0.1.2",
"description": "Representation Synthesis workflow for auditing agent skills in Claude Code.",
"author": {
"name": "RiemaLabs",
"url": "https://github.com/berabuddies"
},
"license": "Apache-2.0",
"homepage": "https://github.com/berabuddies/Semia",
"repository": "https://github.com/berabuddies/Semia",
"keywords": [
"semia",
"skill-audit",
"claude-code",
"datalog",
"sdl"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 47 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.
- 1mo ago First seen · 20 lines scan A 0d2dc4af35e6
semia is a plugin published in the GitHub repository berabuddies/Semia (612 stars, last pushed 1mo ago), licensed Apache-2.0. 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
story-setup
A setup tool that installs writing-project rules, hooks, agents, and instruction files, with checks for recovering and validating sessions.
flightclaw
Search Google Flights, price-track routes and get alerts when fares drop, then book and pay through Duffel. Remembers travellers, companions, loyalty programmes, cards and cabin preferences so options come back ranked for the person asking.
fasterizy
Speed up agent planning, discussion, and docs without losing technical effectiveness. Code stays unchanged.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.