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.
npx agentmods add skills/tyox-all/weave_protocol/hundredmennpx skills add Tyox-all/Weave_Protocol --skill hundredmengit clone --depth 1 https://github.com/Tyox-all/Weave_ProtocolWrote 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/skills/tyox-all/weave_protocol/hundredmen)<a href="https://agentmods.dev/skills/tyox-all/weave_protocol/hundredmen"><img src="https://agentmods.dev/badge/skills/tyox-all/weave_protocol/hundredmen.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00116 | $0.00943 |
| Opus 5 | $0.00058 | $0.00472 |
| Sonnet 5 | $0.00023 | $0.00189 |
| Haiku 4.5 | $0.00012 | $0.00094 |
Grade A, and why
security-inspection 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hundredmen — Real-Time MCP Security Proxy
@weave_protocol/hundredmen intercepts MCP tool calls, analyzes them, and decides whether to allow, block, or require approval. v1.1.0 adds enforcement of WARD.md policies at the interception layer.
When to use
- User has an agent and wants visibility into what tools it's calling
- User wants to gate sensitive operations behind manual approval
- User has a WARD.md and wants it enforced at runtime, not just declared
- User suspects drift: "the agent said X but is doing Y"
- User wants reputation tracking for the MCP servers they use
Gating order
When a tool call hits Hundredmen, the checks run in this order:
- WARD policy (if loaded) — capability/filesystem/network rules from
WARD.md - Reputation — server trust score
- Intent / drift — declared vs actual comparison
- Manual approval — if any earlier gate produced
require_approval
WARD is the first gate. A WARD deny short-circuits everything else.
WARD-related tools
hundredmen_load_ward({ path? })— load a WARD.md (auto-loads./WARD.mdon startup)hundredmen_show_ward()— show currently active policyhundredmen_check_ward({ tool, args })— dry-run a tool call against the policyhundredmen_unload_ward()— disable WARD enforcement
Other key tools
hundredmen_create_session({ agent_id? })hundredmen_declare_intent({ session_id, intent })hundredmen_diff_intent({ session_id })hundredmen_get_live_feed({ since?, limit? })hundredmen_get_pending()/hundredmen_approve_call/hundredmen_block_callhundredmen_check_reputation({ server_id })hundredmen_get_stats()/hundredmen_get_server_stats({ server_id })
Decision rules
| User says | Action |
|---|---|
| "Set up monitoring for my agent" | hundredmen_create_session + hundredmen_declare_intent |
| "What is my agent doing right now" | hundredmen_get_live_feed |
| "Why was this call blocked" | hundredmen_show_ward + check live feed for the blocked call |
| "Will my WARD block X" | hundredmen_check_ward({ tool: 'X', args: {...} }) |
| "I want WARD enforcement on" | hundredmen_load_ward() (loads from CWD or env) |
| "This server seems off" | hundredmen_check_reputation + hundredmen_report_suspicious |
What ships with it
10 files beside SKILL.md 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.
- 5d ago First seen · 69 lines · 116 tokens per session scan A b2a69f726e73
security-inspection is a skill published in the GitHub repository Tyox-all/Weave_Protocol (0 stars, last pushed 12d ago), licensed Apache-2.0. It adds 116 tokens to every session and 943 once invoked, about $0.0006 per session on Opus 5. 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-31.
Other skills, from other repositories
rtc-balance
Check RustChain wallet balance, epoch info, and network status via the public RPC.
panguard
AI agent security platform — audit skills, scan for threats, and run 24/7 protection with 9,700+ detection rules.
blockchain-solana
Use this skill when asked about Solana blockchain, Solana architecture, Proof of History, Solana programming, Anchor framework, Solana runtime, Solana CLI tools, Solana DeFi, Jupiter, Raydium, Metaplex, SPL tokens, and the Solana ecosystem. Covers Solana protocol architecture (PoH, Tower BFT, Turbine, Gulf Stream…
lictor-rotate
Walks the user through rotating a leaked API key — step by step, provider-specific. Knows the exact URL to visit, the exact button to click, and how to verify the rotation worked. Supports Stripe, OpenAI, Anthropic, Google Cloud / AI Studio, GitHub, AWS, Slack, Supabase, Firebase, Postmark, and generic OAuth providers.
alchemy-agentic-gateway
Use when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features. Also use when the user mentions "SIWE", "SIWS", "x402", "MPP", "mppx", or "agentic gateway" — this skill covers wallet-based auth flows for Alchemy's x402 and MPP…
alchemy-api
Integrates Alchemy blockchain APIs using an API key. Requires $ALCHEMYAPIKEY to be set; if unavailable, use the alchemy-agentic-gateway skill instead. Use when user asks about EVM JSON-RPC calls, token balances, NFT ownership or metadata, transfer history, token prices, portfolio data, transaction simulation…