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 hiendinhngoc/unknowns --skill mockgit clone --depth 1 https://github.com/hiendinhngoc/unknownsWrote 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/hiendinhngoc/unknowns/mock)<a href="https://agentmods.dev/skills/hiendinhngoc/unknowns/mock"><img src="https://agentmods.dev/badge/skills/hiendinhngoc/unknowns/mock.svg" alt="Measured on agentmods" 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.00050 | $0.00632 |
| Opus 5 | $0.00025 | $0.00316 |
| Sonnet 5 | $0.00010 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
mock 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 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.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mock Before Wiring
Validate the idea with a disposable prototype. Cheap to throw away, cheap to redo.
Do not touch the real codebase. The prototype lives ONLY in the session scratchpad directory. No production files created or modified.
Process
- Pin down what's being validated. One sentence: "This mock answers: " (e.g. "should filtering be inline or a sidebar?"). If you can't write that sentence, ask the user what's undecided.
- Resolve a disposable location. Prefer a harness-provided scratchpad. If none exists, create a temporary directory outside the repository. Never use an untracked directory inside the project as a substitute.
- Non-web target? Scope the mock's authority first. When the product is
native, CLI, or embedded, say up front what an HTML mock can and cannot
answer. It CAN validate flows, layout, copy, and state transitions; it
CANNOT validate platform feel, native gestures, assistive-technology
behavior, or animation physics. If the undecided question is on the
cannot list, say so and validate in the platform's own cheap medium
instead (a throwaway SwiftUI
#Preview, a--dry-runflag, a bench sketch) — do not fake confidence with a web approximation. - Build one self-contained HTML file in that directory:
- Inline all CSS/JS — no external requests
- Fake all data with hardcoded fixtures; fake all backend calls with setTimeout + canned responses
- Make the undecided part interactive; keep everything else minimal
- Preview with the best available capability. Render it with the Artifact tool when available. If this agent has no Artifact tool, provide the absolute file path and, when supported, open it in a local browser. Do not claim it was previewed when the environment cannot render or open it.
- Iterate. Apply requested changes to the same file. Refresh the existing preview when supported; otherwise provide the unchanged file path.
- Exit. When the user is satisfied, ask: "Does this match what you wanted?" Then extract the confirmed decisions into a short spec in conversation:
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 · 56 lines · 50 tokens per session scan A 7b3c83ccfb66
mock is a skill published in the GitHub repository hiendinhngoc/unknowns (9 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 632 once invoked, about $0.0003 per session on Opus 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
visual-verdict
Structured visual QA verdict for screenshot-to-reference comparisons.
web-design-reviewer
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage…
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
frontend-philosophy
Visual & UI philosophy (The 5 Pillars of Intentional UI). Understand deeply to avoid "AI slop" and create distinctive, memorable interfaces.