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 CCDevelopForFun/agent-controller --skill example-time-skillgit clone --depth 1 https://github.com/CCDevelopForFun/agent-controllerWrote 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/ccdevelopforfun/agent-controller/example-time-skill)<a href="https://agentmods.dev/skills/ccdevelopforfun/agent-controller/example-time-skill"><img src="https://agentmods.dev/badge/skills/ccdevelopforfun/agent-controller/example-time-skill/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/ccdevelopforfun/agent-controller/example-time-skill"><img src="https://agentmods.dev/badge/skills/ccdevelopforfun/agent-controller/example-time-skill.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.00025 | $0.00263 |
| Opus 5.5 | $0.00010 | $0.00105 |
| Sonnet 5.5 | $0.00005 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
example-time-skill 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
Time Formatting
When you report any date or time to the user, always follow these rules:
- Format: Use ISO-8601 format —
YYYY-MM-DDTHH:MM:SSZ(e.g.2025-05-26T14:32:00Z). - Timezone: Always use UTC. Always append the letter
Zto make the timezone explicit. - Label: After the timestamp, always write "(UTC)" in parentheses so the user knows the timezone at a glance.
Examples
| Instead of … | Write … |
|---|---|
| "2:32 PM" | 2025-05-26T14:32:00Z (UTC) |
| "May 26, 3pm EST" | 2025-05-26T20:00:00Z (UTC) |
| "now" | 2025-05-26T14:32:00Z (UTC) |
Always be explicit. Never leave the timezone ambiguous.
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 Changed · +14 lines · +13 tokens per session a62617f55649
- 2mo ago First seen · 9 lines · 12 tokens per session scan A d53952d49e11
example-time-skill is a skill published in the GitHub repository CCDevelopForFun/agent-controller (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 263 once invoked, about $0.0001 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
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
github-issue-to-pr
Implement one scafld-governed repository issue with normal host tools, prove the tested change through its finalize wall, and optionally publish the exact pull request through scoped provider authority with readback.
loop-orchestration
Reference loop-orchestration example; a local loop host chains governed runx runs through receipts, budgets, context, and stop policy.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
loop-operator-context
Advisory operating context for the loop-orchestration example.
engineering-principles
Practical engineering judgement: smallest change, subtract before adding, data structures before logic, idempotent operations, migrate callers then delete. Use when designing, building, or reviewing changes.