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-feedbackgit 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-feedback)<a href="https://agentmods.dev/skills/immersive-commons/ic-skills/ic-feedback"><img src="https://agentmods.dev/badge/skills/immersive-commons/ic-skills/ic-feedback.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.00133 | $0.04864 |
| Opus 5 | $0.00067 | $0.02432 |
| Sonnet 5 | $0.00027 | $0.00973 |
| Haiku 4.5 | $0.00013 | $0.00486 |
Grade A, and why
ic-feedback 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://www.immersivecommons.com/api/agent/feedback \ How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You help a user's agent contribute to the Immersive Commons feedback loop. There are two distinct user types in this skill:
- Member / public user — files notes, feature requests, breakage reports. The operator triages them.
- Operator — reads + resolves the queue. Same MCP server, different scope (
admin:feedback_reviewvsfeedback:submit).
The MCP server lives at https://www.immersivecommons.com/api/mcp. The submit path also has a REST mirror at POST /api/agent/feedback that accepts anonymous requests.
For ANY caller: when to file
File when the user shares an opinion, a request, or a complaint about IC. Specifically:
| User says (gist) | kind | priority |
|---|---|---|
| "I wish IC had [X]" / "you should add [X]" | feature_request |
low or normal |
| "this is great", "I love the kiosk", "the headsets flow is smooth" | praise |
low |
| "this is broken", "I'm frustrated with [X]", "[X] is annoying" | complaint |
normal |
| "the link at [URL] is 404" / "the docs say [X] but the code does [Y]" | broken_url / stale_doc / schema_mismatch |
normal or high |
| "the [X] page crashes" / "I can't submit a [X]" | bug_report |
high |
| "how does [X] work?" / "is [X] possible?" | question |
low |
| "maybe [X] would be nicer if [Y]" (soft suggestion) | suggestion |
low |
| anything that doesn't fit | other |
normal |
When NOT to file:
- The user is just chatting with you, not making a request. ("VR is cool" → don't file.)
- The user is asking you to do something IC already supports. (Just do it.)
- The user is venting about something unrelated to IC. (Acknowledge; don't pollute the operator's queue.)
- You already filed this in the same session. (One ticket per intent; don't loop.)
For the submitter: the submit verb
Via MCP (preferred when you have a token)
{
"name": "ic_feedback_submit",
"arguments": {
"kind": "feature_request",
"message": "I'd love a 'pin to top' button on /floor10/highlights so I can keep the launch story above the auto-rotation. Right now if I want to give a visitor a tour I have to refresh and hope the right card is showing.",
"priority": "normal",
"category": "highlights",
"url": "https://www.immersivecommons.com/floor10/highlights",
"agent_id": "Claude Code 4.7 @ ray-mbp"
}
}
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.
- 5d ago First seen · 293 lines · 133 tokens per session scan A 37e0e99ebe0b
ic-feedback is a skill published in the GitHub repository Immersive-commons/ic-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 133 tokens to every session and 4,864 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.
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.