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 kumar045/Control-PC-Terminal --skill policygit clone --depth 1 https://github.com/kumar045/Control-PC-TerminalWrote 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/kumar045/control-pc-terminal/policy)<a href="https://agentmods.dev/skills/kumar045/control-pc-terminal/policy"><img src="https://agentmods.dev/badge/skills/kumar045/control-pc-terminal/policy/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/kumar045/control-pc-terminal/policy"><img src="https://agentmods.dev/badge/skills/kumar045/control-pc-terminal/policy.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.00012 | $0.00077 |
| Opus 5.5 | $0.00005 | $0.00031 |
| Sonnet 5.5 | $0.00002 | $0.00015 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
Insurance coverage 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 1mo 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.
What it actually says
Insurance coverage
Focus on policy benefits, exclusions, eligibility, and covered services. Prefer concise, accurate answers and call out uncertainty if policy details are missing.
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.
- 1mo ago First seen · 13 lines · 12 tokens per session scan A 702f436eb33c
Insurance coverage is a skill published in the GitHub repository kumar045/Control-PC-Terminal (10 stars, last pushed 8mo ago), licensed MIT. It adds 12 tokens to every session and 77 once invoked, about $0.0000 per session on Opus 5.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-31.
Other skills, from other repositories
peac
Slash commands for working with PEAC signed evidence records.
full-after-care
Tiefe Pflegerunde für ein veröffentlichtes GitHub-Repository (Stufe 2): enthält den vollständigen surface-after-care-Durchlauf und ergänzt ihn um drei teure Schritte — rechtliche Ersteinschätzung über die Law-Checker mit Wiedervorlage nach einem Jahr (Gutachten bleibt gitignored im Repo), Querverweise zu verwandten…
connect-required-verification-information
Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required…
breach-notification-triage
Determines whether a security incident involves personal data, triggers regulatory breach-notification obligations (e.g. GDPR Art. 33/34), and what notification timelines apply.
dsgvo-health-data-compliance
Audits architectural proposals and data schemas for GDPR/DSGVO Article 9 (Special Categories of Personal Data) violations.
gdpr-review
Audits data processing systems, logging mechanisms, and user tracking implementations for compliance with EU GDPR / German DSGVO mandates.