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 TomasWard1/limbo --skill google-calendargit clone --depth 1 https://github.com/TomasWard1/limboWrote 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/tomasward1/limbo/google-calendar)<a href="https://agentmods.dev/skills/tomasward1/limbo/google-calendar"><img src="https://agentmods.dev/badge/skills/tomasward1/limbo/google-calendar/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/tomasward1/limbo/google-calendar"><img src="https://agentmods.dev/badge/skills/tomasward1/limbo/google-calendar.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.00000 | $0.01466 |
| Opus 5.5 | $0.00000 | $0.00586 |
| Sonnet 5.5 | $0.00000 | $0.00293 |
| Haiku 4.5 | $0.00000 | $0.00147 |
Grade A, and why
google-calendar 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 145 lines · 0 tokens per session scan A 19eeb1c22fe7
google-calendar is a skill published in the GitHub repository TomasWard1/limbo (5 stars, last pushed 4mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,466 tokens. 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
sf-tasks
Builds a prioritized task backlog from a Screaming Frog export or audit.json, with a configurable pipeline (which severities to include, grouping by issue type or URL, P1/P2/P3 priorities, effort estimates, and limits). For broken links, each task includes the location (source/destination/position/XPath). Use when…
bo-process-optimization
A method for examining a business workflow to find waiting, rework, handoff waste, and other delays, then proposing improvements and ways to measure them. It separates observed facts from possible explanations and suggestions.
bo-risk-assessment
A method for assessing operational risks in a process, project, or supplier arrangement using observed facts, possible consequences, and practical response suggestions. It keeps the likelihood of a consequence conditional unless the evidence supports more.
bo-status-report
A template and set of rules for writing factual operational status reports for a given period. It covers completed, ongoing, blocked, and measured work without filling gaps with guesses.
bo-vendor-review
A framework for comparing supplier proposals and renewal choices using costs, service terms, operational fit, contracts, and business-continuity risks. It treats one-time, recurring, and usage-based charges separately when comparing prices.
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.