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 agentmods add skills/whynusn/typetype/typetype-adding-featurenpx skills add whynusn/typetype --skill typetype-adding-featuregit 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-adding-feature)<a href="https://agentmods.dev/skills/whynusn/typetype/typetype-adding-feature"><img src="https://agentmods.dev/badge/skills/whynusn/typetype/typetype-adding-feature.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.00036 | $0.01101 |
| Opus 5 | $0.00018 | $0.00550 |
| Sonnet 5 | $0.00007 | $0.00220 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
typetype-adding-feature 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 6d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeType: Adding New Feature Workflow
Follow these steps IN ORDER.
Step 1: Understand & Plan
- Read requirement carefully
- Check
typetype-architecturefor layering rules - Identify which layers to modify
Decision: Need UseCase?
| Situation | Decision |
|---|---|
| Requires cross-component orchestration/routing | ✅ Create UseCase in application/usecases/ |
| Single pure business service call | ✅ Adapter → Domain directly, NO UseCase |
Decision: Need new Port?
| Situation | Decision |
|---|---|
| New external dep that could have multiple implementations | ✅ Define protocol in ports/ |
| One implementation only, not expected to vary | ❌ No Port needed |
Step 2: Identify Files
| Feature Type | Files to modify/create |
|---|---|
| New text source | 1. ports/text_provider.py (if new protocol)2. integration/xxx.py (impl)3. User config config.json 添加新 source key4. Update main.py injection and/or TextSourceGateway only if routing changes5. Add test |
| New business | 1. domain/services/xxx.py2. presentation/adapters/xxx.py3. presentation/bridge.py (signals/slots if needed)4. Add test |
| New UI page | 1. src/qml/pages/Page.qml2. Update Main.qml nav3. bridge.py if needed4. Python adapter if needed |
| New persistence | 1. ports/repo.py (protocol)2. integration/sqlite-repo.py (impl)3. Domain Service uses it4. Add test |
Step 3: Verify Architecture Rules BEFORE Coding
- No forbidden dependencies (e.g., Qt import in Domain)
- Business routing in Application (not Adapter)
- Domain is pure business logic → NO Qt
- Dependency direction correct:
Presentation → Application → Domain/Ports → Integration
Step 4: Write Code
- Follow
typetype-coding-standardsfor naming/types/imports - Write tests alongside code →
tests/test_xxx.py - TDD: write failing test first → write code → pass
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.
- 6d ago First seen · 140 lines · 36 tokens per session scan A 4f29c0290fe1
typetype-adding-feature is a skill published in the GitHub repository whynusn/typetype (11 stars, last pushed 19d ago), licensed MIT. It adds 36 tokens to every session and 1,101 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
add-crate
Add a new member crate to a Cargo workspace in this repo using the y5-template binary. Use whenever the user asks to add/create/scaffold a new crate, module, or workspace member (e.g. "add a crate under compositor.window", "scaffold action.foo"). Handles the chain-prefix naming convention and non-interactive…
logging
How to log in the y5 compositor. Use whenever you add, change, or migrate logging — any time you'd reach for a log/print statement, "add a log", debug output, tracing::!, println!, or a fatal panic! with a message. y5 has its own tracing-free structured logging; this skill is the source of truth for using it.
perf-audit
Full performance/concurrency audit of Unisic (C++/Qt6/QML, Wayland). Use when the user asks for a performance audit, "make app fast", idle CPU/memory investigation, memory leaks, thread bugs, deadlocks, or invokes /perf-audit. Measurement-first — never guess; produces a structured report and minimal fixes.
ponytail-perf-audit
Ponytail-style performance/concurrency audit of Unisic (C++/Qt6/QML, Wayland): lazy senior engineer, evidence-first, NO code changes during the audit. Produces a verdict/baseline/ranked-findings report in the strict P tag format. Use when the user says "ponytail audit", "audyt wydajności ponytail"…
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.