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 tph-kds/deckforge --skill deckforge-visual-evidencegit clone --depth 1 https://github.com/tph-kds/deckforgeWrote 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/tph-kds/deckforge/deckforge-visual-evidence)<a href="https://agentmods.dev/skills/tph-kds/deckforge/deckforge-visual-evidence"><img src="https://agentmods.dev/badge/skills/tph-kds/deckforge/deckforge-visual-evidence/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/tph-kds/deckforge/deckforge-visual-evidence"><img src="https://agentmods.dev/badge/skills/tph-kds/deckforge/deckforge-visual-evidence.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.00071 | $0.00319 |
| Opus 5.5 | $0.00028 | $0.00128 |
| Sonnet 5.5 | $0.00014 | $0.00064 |
| Haiku 4.5 | $0.00007 | $0.00032 |
Grade A, and why
deckforge-visual-evidence 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
deckforge-visual-evidence
Verification worker. Prove a generated DeckForge application works by executing it.
- Determine changed surfaces and the required capabilities from the capability catalog.
- Start the target application on an isolated port (do not reuse a shared server).
- Run behavior-focused editor, presenter, viewer, and export-preview scenarios via Playwright.
- Capture the required viewports and a reduced-motion run.
- Record console errors, failed requests, and timing.
- Retry each candidate defect once before reporting.
- Annotate evidence with slide, block, and capability IDs.
- Generate
browser-evidence-report.jsonand per-capability evidence entries. - Stop all created processes and browser contexts.
- Mark unavailable checks
unverified, neverpassed.
Read references/browser-evidence-contract.md and the report schema at
../../schemas/browser-evidence-report.schema.json. Map Playwright tests to
capabilities with assets/evidence-capability-map.json.
Never claim a check ran when the browser, runner, or port was unavailable.
What ships with it
2 files 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.
- 1mo ago First seen · 29 lines · 71 tokens per session scan A 6b56b723ab96
deckforge-visual-evidence is a skill published in the GitHub repository tph-kds/deckforge (4 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 319 once invoked, about $0.0003 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
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
nexent-daily-test
A procedure for running Nexent daily, full-layer tests on a self-hosted Ubuntu machine. Nexent is tested across separate layers such as unit, service, AI runtime, and browser journeys, with results and evidence kept locally.
tfp-verification
Generate a deterministic report for disposable executor acceptance tests.
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.
06-test
Write and iterate developer-side tests until they pass, or validate a user journey end to end in the browser during implementation. Use when the user wants to add coverage, find what's untested, or walk a flow while building it. Do NOT use for independent acceptance QA or reviewer evidence, auditing test health, or…