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 skills add Tyox-all/Weave_Protocol --skill yoxallismusgit 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/yoxallismus)<a href="https://agentmods.dev/skills/tyox-all/weave_protocol/yoxallismus"><img src="https://agentmods.dev/badge/skills/tyox-all/weave_protocol/yoxallismus.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.00000 | $0.00570 |
| Opus 5 | $0.00000 | $0.00285 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
yoxallismus 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 7d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔐 Skill: pq-crypto
You have access to @weave_protocol/yoxallismus — an EXPERIMENTAL post-quantum cryptographic composition layer. NOT AUDITED. Use with care.
When to invoke
Use PQ crypto when the user:
- Asks about post-quantum encryption or NIST FIPS 203 (ML-KEM)
- Wants to encrypt data with hybrid classical + post-quantum security
- Is building a system that needs harvest-now-decrypt-later resistance
- Needs a Signal-style ratchet for forward secrecy
- Asks about "quantum-safe" or "PQ-hybrid" cryptography
Key exports
import { PQCipher } from '@weave_protocol/yoxallismus';
// Simple encrypt-to-recipient facade
const alice = PQCipher.generateKeypair();
const bundle = PQCipher.encryptTo(PQCipher.publicKeyOf(alice), plaintext);
const decrypted = PQCipher.decryptFrom(alice, bundle.ciphertext, bundle.payload);
Lower-level primitives also exported:
generateHybridKeypair,encapsulate,decapsulate— hybrid KEMaeadEncrypt,aeadDecrypt— AES-256-GCM AEADhkdf,deriveAeadKey,deriveNonce— HKDF-SHA-256 KDFinitRatchet,ratchetEncrypt,ratchetDecrypt— symmetric ratchetserialize*/deserialize*— wire format helpers
CLI commands
weave-yoxall status— library status + known limitationsweave-yoxall keygen --out=<name>— generate keypairweave-yoxall encrypt --to=<pub> --in=<file>— encrypt fileweave-yoxall decrypt --with=<priv> --in=<file>— decrypt fileweave-yoxall test— reproducible-claims test suiteweave-yoxall audit-self— known-attack test vectorsweave-yoxall benchmark— micro-benchmarks
Critical caveats
- NOT AUDITED. Do not use for regulated, medical, financial, or legal data.
- Wire format may break between v0.1 and v0.2.
- No post-compromise recovery yet (planned v0.2 via DH double-ratchet).
- No threshold encryption yet (planned v0.3).
- Silence the runtime beta banner with
YOXALL_SILENCE_BETA_WARNING=1.
Always point users to THREAT_MODEL.md and SECURITY.md before recommending adoption.
What ships with it
17 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.
- package-lock.json 2.5 KB
- package.json 1.3 KB
- README.md 7.9 KB
- SECURITY_ADVISORIES.md 814 B
- SECURITY.md 4.8 KB
- src/aead.ts 4.1 KB runs code
- src/cli.ts 18 KB runs code
- src/index.ts 4.1 KB runs code
- src/kdf.ts 2.1 KB runs code
- src/kem.ts 7.4 KB runs code
- src/labels.ts 2.8 KB runs code
- src/ratchet.ts 4.0 KB runs code
- src/serialize.ts 3.6 KB runs code
- src/types.ts 2.7 KB runs code
- src/v1-compat.ts 922 B runs code
- THREAT_MODEL.md 9.2 KB
- tsconfig.json 409 B
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.
- 7d ago First seen · 51 lines · 0 tokens per session scan A 7fe265ff72d8
yoxallismus is a skill published in the GitHub repository Tyox-all/Weave_Protocol (0 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 570 tokens. 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
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-security-check
Pre-release security audit for ANY project — AI-built or hand-written, web or mobile. Scans the codebase for the full range of real-world risks that get apps breached: leaked API & AI-provider keys, exposed configs/secrets, broken auth & access control (IDOR), injection (SQL/XSS/command), SSRF, open databases & cloud…
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…