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 whynusn/typetype --skill typetype-coding-standardsgit clone --depth 1 https://github.com/whynusn/typetypeWrote 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/whynusn/typetype/typetype-coding-standards)<a href="https://agentmods.dev/skills/whynusn/typetype/typetype-coding-standards"><img src="https://agentmods.dev/badge/skills/whynusn/typetype/typetype-coding-standards.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.00035 | $0.01036 |
| Opus 5 | $0.00017 | $0.00518 |
| Sonnet 5 | $0.00007 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
typetype-coding-standards 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeType Coding Standards
Python
Import Order
One blank line between groups:
# 1. Standard library
import os
import sys
# 2. Third-party
from PySide6.QtCore import QUrl
import darkdetect
# 3. Local
from src.backend.application.gateways.score_gateway import ScoreGateway
Naming
| Type | Convention | Example |
|---|---|---|
| Class | PascalCase | TextSourceGateway, LoadTextUseCase |
| Function/Variable | snake_case | load_text, source_key |
| File | snake_case / lowercase with underscores | text_source_gateway.py |
| Constant | UPPER_SNAKE_CASE | MAX_RETRIES, DEFAULT_TIMEOUT |
Type Hints
ALL function parameters and return values MUST have type hints.
# Good
def load_text(self, source_key: str) -> str | None: ...
# Bad - missing
def load_text(self, source_key): ...
Line Length
- Max 88 chars (ruff default)
- Long imports/URLs allowed to exceed
Exceptions
- External I/O (network/file) MUST have exception handling
- Network exceptions:
infrastructure/network_errors.py - Global → user message:
application/exception_handler.py
Qt/QML
Python/Qt
- Use
Signal()+@Slot()for connections - Blocking operations MUST run in background worker (
QRunnableviaQThreadPool) - Follow
BaseWorkerpattern
QML
- Use
Property+notify signalfor reactive updates - Prefer signal-slot over direct property access
- Colors:
Theme.currentTheme.colors.* - Normal UI font follows the global app font set in
main.py; only dedicated reading/typing areas should set a customfontFamily(current example:TypingPage.qmluses LXGW WenKai for正文区) - Name conflict:
import RinUI as RinthenRin.TextArea
Architecture Rules (MUST Follow)
- Domain Services are pure → NO
import PySide6indomain/services/ - Dependency inward only → outer → inner, never reverse
- Program to interface → use Ports (protocols) for external deps
- Routing in Application → Adapters don't make routing decisions
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 First seen · 137 lines · 35 tokens per session scan A c23516884b46
typetype-coding-standards is a skill published in the GitHub repository whynusn/typetype (11 stars, last pushed 20d ago), licensed MIT. It adds 35 tokens to every session and 1,036 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-30.
Other skills, from other repositories
analyzing-linux-elf-malware
Analyze malicious Linux ELF binaries — botnets, cryptominers, ransomware, and rootkits targeting Linux servers, containers, and cloud infrastructure — through static analysis, dynamic tracing, and reverse engineering of x8664 and ARM samples. Use when investigating Linux malware, triaging a suspicious ELF binary…
analyzing-linux-kernel-rootkits
Detect kernel-level rootkits in Linux memory dumps using Volatility3 linux plugins (checksyscall, lsmod, hiddenmodules), rkhunter system scanning, and /proc vs /sys discrepancy analysis to identify hooked syscalls, hidden kernel modules, and tampered system structures.
create-skill
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
figma-create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server…
figma-generate-library
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. This skill teaches WHAT to build and in WHAT ORDER — it…
figma-implement-design
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via…