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 Devin-AXIS/iPolloWork --skill daytona-windows-certgit clone --depth 1 https://github.com/Devin-AXIS/iPolloWorkWrote 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/devin-axis/ipollowork/daytona-windows-cert)<a href="https://agentmods.dev/skills/devin-axis/ipollowork/daytona-windows-cert"><img src="https://agentmods.dev/badge/skills/devin-axis/ipollowork/daytona-windows-cert.svg" alt="Measured on agentmods" 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.00057 | $0.03494 |
| Opus 5 | $0.00028 | $0.01747 |
| Sonnet 5 | $0.00011 | $0.00699 |
| Haiku 4.5 | $0.00006 | $0.00349 |
Grade A, and why
daytona-windows-cert 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 8d 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.
prerelease**, and download it inside the VM with the Windows-bundled `curl.exe` The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 8d ago First seen · 346 lines · 57 tokens per session scan A 29376ae6a8cb
daytona-windows-cert is a skill published in the GitHub repository Devin-AXIS/iPolloWork (5,435 stars, last pushed today), with no licence file. It adds 57 tokens to every session and 3,494 once invoked, about $0.0003 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-30.
Other skills, from other repositories
verification
Verify that ChatCut plugin edits are reflected in project structure and visible timeline output before reporting success.
e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
browser-qa
Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
acceptance-test-authoring
Use when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an acceptance stack, or implementing OpenSpec tasks that involve acceptance tests.
diagnosing-bugs
Use when debugging a bug, test failure, or unexpected behavior, before proposing fixes. Build a tight red-capable feedback loop first, then reproduce, hypothesise, instrument, fix, and clean up.