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 jongwony/epistemic-protocolsnpx agentmods add plugins/jongwony/epistemic-protocols/horismosgit clone --depth 1 https://github.com/jongwony/epistemic-protocolsWrote 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/jongwony/epistemic-protocols/horismos)<a href="https://agentmods.dev/plugins/jongwony/epistemic-protocols/horismos"><img src="https://agentmods.dev/badge/plugins/jongwony/epistemic-protocols/horismos.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
horismos 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 today.
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": "horismos",
"description": "Define epistemic boundaries per decision — /bound (ὁρισμός: a bounding)",
"version": "3.0.3",
"author": {
"name": "Jongwon Choi",
"url": "https://github.com/jongwony"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 41 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.
- today Changed b8c34f634c46
- 4d ago First seen · 10 lines scan A 55f03a833fee
horismos is a plugin published in the GitHub repository jongwony/epistemic-protocols (160 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
uniswap-cca
Configure and deploy Continuous Clearing Auction (CCA) smart contracts for token distribution.
spec-first marketplace
Spec-first development: define a spec, implement it, and generate docs.
pwdev-copy
Framework de copy genérico e treinável — um arquivo de contexto define marca, ICP e voz, e 20 skills cobrem o ciclo completo: pesquisa VOC, brand voice, criação (landing, social, ganchos, reaproveitamento), revisão em 7 sweeps com anti-slop, e camada de análise que fecha o loop (perf-analyzer, perf-patterns…
lendwise
Unified view for lending markets, one standard. Compare and optimize DeFi supply/borrow across Aave, Morpho and Compound. Read-only; it never signs a transaction.
solidity-auditor
Professional smart contract security audits with OWASP Top 10 coverage.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.