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 Whytcard-Swiss-AI/wsai_fckdot --skill wsai_fckdot-usegit clone --depth 1 https://github.com/Whytcard-Swiss-AI/wsai_fckdotWrote 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/whytcard-swiss-ai/wsai_fckdot/wsai_fckdot-use)<a href="https://agentmods.dev/skills/whytcard-swiss-ai/wsai_fckdot/wsai_fckdot-use"><img src="https://agentmods.dev/badge/skills/whytcard-swiss-ai/wsai_fckdot/wsai_fckdot-use/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/whytcard-swiss-ai/wsai_fckdot/wsai_fckdot-use"><img src="https://agentmods.dev/badge/skills/whytcard-swiss-ai/wsai_fckdot/wsai_fckdot-use.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.00035 | $0.00540 |
| Opus 5 | $0.00017 | $0.00270 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
wsai_fckdot-use 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 11d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use wsai_fckdot
Use this skill when a user reports a technical failure that may involve hooks, plugins, skills, MCP, local configuration, runtimes, networking, permissions, or system state.
Privacy and control rules
- Start from user-supplied symptoms; do not collect the PC by default.
- Call
get_control_catalogoraudit_coveragebefore collection when scope is unclear. - Call
collect_contextfirst withexecute=falseto show the exact plan. - Execute probes only with explicit approval represented by both
execute=trueandconsent=true. - Keep
include_output=falseunless redacted output is necessary for the diagnosis. - Never apply a proposed fix automatically. Ask before any mutation, installation, restart, permission change, deletion, or configuration edit.
- For multi-tool setup conflicts, hand off to the
wsai_fckdot-setupworkflow; do not treat setup application as diagnostic collection. - Treat a runtime coverage below 100% as incomplete observation, not as a healthy machine.
Diagnostic workflow
- Normalize the problem into
description,problem_type, relevant logs and secret-free configuration fragments. - Call
diagnoseimmediately on the supplied evidence. - Read findings in severity and confidence order.
- Identify the smallest relevant controls from the 38-control catalog.
- Plan those controls with
collect_context(execute=false). - If the user approves, run only those controls with strict redaction.
- Add returned observations to a second
diagnosecall. - Distinguish confirmed evidence, probable causes, unknowns and proposed corrections.
- Re-run the same controls after an authorized correction to verify the change.
Tool selection
diagnose: rank causes from a concrete problem.list_diagnostics: inspect the 15 registered rule families.get_control_catalog: choose controls without touching the host.audit_coverage: measure catalog design coverage only.collect_context: plan or explicitly run allowlisted read-only probes.run_self_test: validate the diagnostic engine using synthetic public cases.
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.
- 11d ago First seen · 51 lines · 35 tokens per session scan A dfd4d794c4b1
wsai_fckdot-use is a skill published in the GitHub repository Whytcard-Swiss-AI/wsai_fckdot (0 stars, last pushed 29d ago), licensed MIT. It adds 35 tokens to every session and 540 once invoked, about $0.0002 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.