Borrowing it
Nothing to install: this file belongs to verivus-oss/llm-cli-gateway. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/verivus-oss/llm-cli-gateway/main/.agents/skills/public-demo-session/SKILL.mdgit clone --depth 1 https://github.com/verivus-oss/llm-cli-gatewayWrote 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/verivus-oss/llm-cli-gateway/public-demo-session)<a href="https://agentmods.dev/skills/verivus-oss/llm-cli-gateway/public-demo-session"><img src="https://agentmods.dev/badge/skills/verivus-oss/llm-cli-gateway/public-demo-session/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/verivus-oss/llm-cli-gateway/public-demo-session"><img src="https://agentmods.dev/badge/skills/verivus-oss/llm-cli-gateway/public-demo-session.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01015 |
| Opus 5 | $0.00027 | $0.00508 |
| Sonnet 5 | $0.00011 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
public-demo-session 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 11d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Public Demo Session
Use this skill when the goal is a public recording, README demo, screenshot, or clean transcript. The priority is a short, reliable demo surface, not exhaustive orchestration.
Goals
- Show only a public-safe workspace path such as
/llm-cli-gateway. - Keep the llm-cli-gateway MCP server and workspace skills available.
- Prefer direct, synchronous provider calls that return compact text.
- Avoid validation wrappers, async polling, nested Codex, and repeated stuck-job polling unless the user explicitly asks for those features.
Full-access review handoff
A public demo is not a review shortcut. If the user explicitly asks for a
full-access, native-MCP, evidence-backed review, leave demo mode and follow the
multi-llm-review full-access protocol. Build the exact target checkout and
launch node dist/index.js --transport=stdio from it, rather than using a demo
or globally installed gateway. Reapply the provider-native grant per new job,
send the corrective-program verification report and exact diff/file identity,
require independent code/docs/tests inspection, set no caller caps, and honor a
user-required 90-second progress cadence. Do not use direct provider calls or a
public demo home as a substitute for that review path.
Path Hygiene
Do not start Codex directly from an internal checkout path for public demos. A symlink may still leak a resolved path in some tools. Prefer a bind-mounted public path:
bwrap \
--bind "$REAL_REPO" /llm-cli-gateway \
--chdir /llm-cli-gateway \
--setenv CODEX_HOME "$DEMO_CODEX_HOME" \
codex --dangerously-bypass-approvals-and-sandbox
If the host needs Codex HTTPS/WebSocket support inside the mount namespace, bind the host CA backing store too. On this host /etc/ssl/certs depends on /var/lib/ca-certificates.
The demo CODEX_HOME should have a minimal config.toml with:
model = "gpt-5.5"
model_reasoning_effort = "high"
project_doc_max_bytes = 0
[projects."/llm-cli-gateway"]
trust_level = "trusted"
[mcp_servers.llm-gateway]
command = "node"
args = ["/llm-cli-gateway/dist/index.js"]
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.
- 11d ago First seen · 114 lines · 54 tokens per session scan A 739b1434bb3f
public-demo-session is a skill published in the GitHub repository verivus-oss/llm-cli-gateway (15 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,015 once invoked, about $0.0003 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-30.
Other skills, from other repositories
provider-integration
Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface. Covers creating provider shell scripts, setting API keys, and validating connectivity. Triggers on "add provider", "new AI agent", "provider not working", "API…
architect
System design, tradeoffs, and complex technical decisions.
security-analyst
Threat-model and find vulnerabilities, with practical remediation.
plan-reviewer
Validate that a work plan is executable before work starts.
researcher
Research external libraries, APIs, and best practices, with evidence.
debugger
Rank root-cause hypotheses and propose the smallest safe fix.