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 Immersive-commons/ic-skills --skill ic-signed-agentgit clone --depth 1 https://github.com/Immersive-commons/ic-skillsWrote 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/immersive-commons/ic-skills/ic-signed-agent)<a href="https://agentmods.dev/skills/immersive-commons/ic-skills/ic-signed-agent"><img src="https://agentmods.dev/badge/skills/immersive-commons/ic-skills/ic-signed-agent.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.00122 | $0.03098 |
| Opus 5 | $0.00061 | $0.01549 |
| Sonnet 5 | $0.00024 | $0.00620 |
| Haiku 4.5 | $0.00012 | $0.00310 |
Grade A, and why
ic-signed-agent scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
return fetch(url, { How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You help an agent's human bind an Ed25519 keypair to an existing IC agent token, then sign every subsequent request. The threat model: bearer tokens are bearer-only — leak the plaintext, the holder can act as you until you revoke. With signature enforcement on, a leaked bearer plus the canonical signature base is meaningless without the private key your agent generated locally and never shares.
Pre-flight (always)
-
Existing IC agent token. Need an
agt_*bearer inFLOOR10_AGENT_TOKEN(or equivalent) with at least one scope. If the agent doesn't have one yet, run@ic-onboardingfirst. -
Modern crypto stack. The agent runtime needs Ed25519 support:
- Node 20+ (Web Crypto:
crypto.subtle.generateKey({name: "Ed25519"}, ...)) - Python 3.11+ with
cryptography>=42(Ed25519PrivateKey.generate()) - Browsers: Chrome 113+, Firefox 130+, Safari 17+ If the runtime can't do Ed25519, stop — this skill doesn't apply.
- Node 20+ (Web Crypto:
-
Browser handy for the human. Key registration is Clerk-gated by design (a leaked bearer must NOT be able to bind a new key — that would let an attacker lock the legitimate user out). The human signs in at https://www.immersivecommons.com/membership, clicks Register a key for one of their tokens.
The pipeline (always this order)
1. Generate the keypair locally
TypeScript / Node:
const kp = await crypto.subtle.generateKey(
{ name: "Ed25519" },
/* extractable */ true,
["sign", "verify"],
);
// Export the PUBLIC key only; keep the private key in-memory or in your
// runtime's secure store. Never send the private key anywhere.
const pubJwk = await crypto.subtle.exportKey("jwk", kp.publicKey);
// pubJwk shape:
// { kty: "OKP", crv: "Ed25519", x: "<43-char base64url>", alg: "EdDSA", key_ops: ["verify"] }
Python:
from cryptography.hazmat.primitives.asymmetric.ed25519 import Ed25519PrivateKey
from cryptography.hazmat.primitives import serialization
import base64, json
priv = Ed25519PrivateKey.generate()
pub_bytes = priv.public_key().public_bytes(
encoding=serialization.Encoding.Raw,
format=serialization.PublicFormat.Raw,
)
pub_jwk = {
"kty": "OKP",
"crv": "Ed25519",
"x": base64.urlsafe_b64encode(pub_bytes).rstrip(b"=").decode(),
"alg": "EdDSA",
}
# Stash `priv` in your secret store; serialize `pub_jwk` to JSON for the bind step.
What ships with it
1 file 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.
- 6d ago First seen · 259 lines · 122 tokens per session scan A 0f6a7963d0f2
ic-signed-agent is a skill published in the GitHub repository Immersive-commons/ic-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 122 tokens to every session and 3,098 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
develop
Work on any Mantle project using the Core SDK contract. Use for manifest, runtime, content model, handler, adapter, validation, and MCP work after a project already exists.
install
Start a new Mantle site locally from a deterministic starter bundle, or orient and continue an existing local or Mantle landing project. Use when the user gives a Mantle repository URL and asks to try or build with it, invokes the Mantle install skill, wants a new Mantle site, or opens an existing generated site.
provision
Ship a local or Mantle landing-generated project to Cloudflare and finish production auth. Use when a Mantle project is ready for GitHub, Cloudflare deployment, self-hosted GitHub OAuth, paid Mantle hosted auth verification, production smoke testing, or operator handoff.
plugin
Discover, plan, apply, and verify Mantle marketplace plugins through the Core SDK contract. Use when the user wants to add an installable capability without hand-planning provisioning steps.
theme
Apply brand and visual direction in a generated Mantle project using its repo-owned theme and UI contracts.
update
Check a Mantle project for drift against its Core SDK, starter source, or installed plugin lockfiles.