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-signalgit 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-signal)<a href="https://agentmods.dev/skills/immersive-commons/ic-skills/ic-signal"><img src="https://agentmods.dev/badge/skills/immersive-commons/ic-skills/ic-signal/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/skills/immersive-commons/ic-skills/ic-signal"><img src="https://agentmods.dev/badge/skills/immersive-commons/ic-skills/ic-signal.svg" alt="Reviewed on agentmods" width="80" 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.00143 | $0.01639 |
| Opus 5 | $0.00072 | $0.00820 |
| Sonnet 5 | $0.00029 | $0.00328 |
| Haiku 4.5 | $0.00014 | $0.00164 |
Grade A, and why
ic-signal 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 9d 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.
curl -sS -X POST https://www.immersivecommons.com/api/mcp \ How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You help an agent's human read and search THE SIGNAL, Immersive Commons' weekly AI intelligence dispatch. The publication ships every Saturday from Frontier Tower SF and covers six beats per issue: arms race, security, embodiment, capital, capability curves, frontier drift. Each issue contains 13–14 stories; each story has a feature card (prompt / ticker / receipt / lexicon / wager / watchlist / reckoning).
Five public (no-token) MCP tools at https://www.immersivecommons.com/api/mcp:
ic_signal_list_issues({ limit? })— issue summaries, newest first.ic_signal_get_latest()— the most-recent issue summary (convenience).ic_signal_get_issue({ slug })— full issue tree (beats + stories + meta + sources).ic_signal_get_story({ slug, story_id })— single story.ic_signal_search({ q, limit? })— ranked substring hits across every issue.
No Authorization: Bearer header needed. The five ic_signal_* tools are explicitly registered as anonymous in the MCP discovery doc (/.well-known/mcp.json public_tools field).
Pre-flight (every session)
Smoke probe — anonymous tools/call, no bearer:
curl -sS -X POST https://www.immersivecommons.com/api/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ic_signal_get_latest","arguments":{}}}'
200 + a JSON result with a slug field = good. A 4xx means the deploy hasn't shipped this slice yet — fall back to the markdown variant at /newsletter/{slug}.md.
The four common flows
A. "What's in the latest SIGNAL?"
-
Get the summary.
{ "name": "ic_signal_get_latest", "arguments": {} }Returns
{ slug, number, title, dek, datespan, published, story_count, beat_count, html_url, markdown_url }. Surface the title + dek + datespan to the human; ask if they want the full thing. -
If yes, fetch the tree.
{ "name": "ic_signal_get_issue", "arguments": { "slug": "<slug from step 1>" } }Returns the full issue tree. For LLM ingest, prefer the markdown URL —
GET https://www.immersivecommons.com/newsletter/{slug}.md— which is ~70% smaller than the JSON tree.
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.
- 9d ago First seen · 110 lines · 143 tokens per session scan A 905772cf86de
ic-signal is a skill published in the GitHub repository Immersive-commons/ic-skills (0 stars, last pushed yesterday), licensed MIT. It adds 143 tokens to every session and 1,639 once invoked, about $0.0007 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.
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.
install
Author a new Mantle application directly from version-matched SDK docs, or continue an existing project. Use when asked to install Mantle, build a Mantle application, or open a Mantle repository.
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 Mantle application using its repo-owned theme and UI contracts.
update
Review and upgrade Mantle SDK dependencies and project-local skills while preserving application source, provider identities and plugin lockfiles.