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 yogasw/wick --skill wick-agent-cardsgit clone --depth 1 https://github.com/yogasw/wickWrote 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/yogasw/wick/wick-agent-cards)<a href="https://agentmods.dev/skills/yogasw/wick/wick-agent-cards"><img src="https://agentmods.dev/badge/skills/yogasw/wick/wick-agent-cards/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/yogasw/wick/wick-agent-cards"><img src="https://agentmods.dev/badge/skills/yogasw/wick/wick-agent-cards.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.00115 | $0.01207 |
| Opus 5.5 | $0.00046 | $0.00483 |
| Sonnet 5.5 | $0.00023 | $0.00241 |
| Haiku 4.5 | $0.00012 | $0.00121 |
Grade A, and why
wick-agent-cards 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Action cards
An action card is a small card with a title, a few key/value rows and optional buttons, drawn in the wick web chat from a fenced block you write. Use one when the user's next step is a click, not a sentence.
The fence
Write a fenced block with the language actioncard and ONE JSON object:
```actioncard
{"id":"rekap-proposal","icon":"shield","title":"New agent: \"Daily Recap\"",
"subtitle":"Persona ready · access and routine need your approval","status":"waiting",
"rows":[["Persona","Daily support recap: yesterday's Slack threads + changed Notion tickets."],
["Connector","Notion · read only"],["Routine","Every day 09:00 → #support-daily"]],
"actions":[{"label":"Approve & create","value":"approve","style":"primary"},
{"label":"Edit first","value":"edit"},{"label":"Reject","value":"reject","style":"ghost"}]}
```
| Field | Required | Meaning |
|---|---|---|
id |
yes | Stable id for this decision. Same id later = the same card, updated. |
title |
yes | One line. |
icon |
no | Short icon name (shield, check, clock, user, …). |
subtitle |
no | One line under the title. |
status |
no | Badge text (waiting, approved, running 2/5, …). |
rows |
no | [["Key","Value"], …]; values may contain \n. Keep it under ~6 rows. |
actions |
no | Buttons: label (shown), value (sent back), style = primary / ghost / omitted. |
final |
no | true locks the buttons — the decision is made. |
Rules:
- The JSON must be valid and the block must be closed. Invalid JSON is shown as a plain code block — the user sees raw text, nothing breaks.
- One decision per card. Do not put two unrelated questions on one card.
- Write a sentence of normal text around the card; the card is not the whole answer.
Updating a card (live status)
Write a new fence with the same id in a later reply. The newest one
replaces the old one in the thread (the old one is shown collapsed), so a
card moves waiting → approved instead of piling up. Add "final":true
when nothing more can be clicked. A new version without final re-opens
the buttons — only do that when you really want a new decision.
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.
- 9d ago First seen · 98 lines · 115 tokens per session scan A 099dfa889924
wick-agent-cards is a skill published in the GitHub repository yogasw/wick (3 stars, last pushed 3d ago), licensed MIT. It adds 115 tokens to every session and 1,207 once invoked, about $0.0005 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-10-06.
Other skills, from other repositories
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-rust
This is an OMH rust workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
workflow-builder
Load before calling build-workflow. Default path for all single-workflow work: new one-off workflows, existing-workflow edits, verification repairs, and workflow-local data tables. Write or edit a workspace source file, run workflow-sdk validate via workspaceexecutecommand, then call build-workflow with filePath. When…
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…