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 tetherto/wdk-agent-skills --skill code-of-conductgit clone --depth 1 https://github.com/tetherto/wdk-agent-skillsWrote 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/tetherto/wdk-agent-skills/code-of-conduct)<a href="https://agentmods.dev/skills/tetherto/wdk-agent-skills/code-of-conduct"><img src="https://agentmods.dev/badge/skills/tetherto/wdk-agent-skills/code-of-conduct/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/tetherto/wdk-agent-skills/code-of-conduct"><img src="https://agentmods.dev/badge/skills/tetherto/wdk-agent-skills/code-of-conduct.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.00137 | $0.04451 |
| Opus 5 | $0.00068 | $0.02226 |
| Sonnet 5 | $0.00027 | $0.00890 |
| Haiku 4.5 | $0.00014 | $0.00445 |
Grade A, and why
code-of-conduct 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 7d 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 — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WDK Code of Conduct
Binding rules every contributor — human or AI coding assistant — MUST follow when writing, modifying, or reviewing code for any Wallet Development Kit (WDK) module (wallets, protocols, core).
- When writing or changing WDK code, comply with every applicable rule before you consider the work done.
- When reviewing WDK code, flag each violation, cite its rule ID, and propose a concrete fix.
The rules are repository-agnostic. No WDK module is a "golden reference" — apply every rule to every module equally. If existing code conflicts with a rule, the code is the candidate for change, not the rule.
Rules are grouped by prefix: P = project & workflow, C = code, T = testing.
| ID | Rule |
|---|---|
| P001 | Pull requests should only include single features |
| P002 | Design, then implement |
| C001 | Avoid code smells |
| C002 | Code should never violate S.O.L.I.D. principles |
| C003 | Provide proper documentation for all public and protected components |
| C004 | Use narrow types for properties and methods |
| C005 | Avoid defensive programming |
| C006 | Always mark errors that a method can throw |
| T001 | Follow the arrange, act, assert pattern |
| T002 | Test only components that are part of the public API |
| T003 | Always test against real values, not properties |
| T004 | Define and assign jest functions at the top level, stub them in test cases |
| T005 | Mock all depended-on components that interact with external services |
Related skills:
wdk-review-jsdocs(JSDoc & type-annotation conventions) andwdk-review-dts(.d.tsmaintenance) enforce the conventions behind C003/C004 in depth;wdk-review-testsenforces the T-rules in depth. Reach for them when you want a focused review of an existing file.
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.
- 7d ago Changed 89024b4a748f
- 11d ago First seen · 415 lines · 137 tokens per session scan A 4be3f3247511
code-of-conduct is a skill published in the GitHub repository tetherto/wdk-agent-skills (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 137 tokens to every session and 4,451 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…