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 wasintoh/toh-framework --skill dev-engineergit clone --depth 1 https://github.com/wasintoh/toh-frameworkWrote 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/wasintoh/toh-framework/dev-engineer)<a href="https://agentmods.dev/skills/wasintoh/toh-framework/dev-engineer"><img src="https://agentmods.dev/badge/skills/wasintoh/toh-framework/dev-engineer/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/wasintoh/toh-framework/dev-engineer"><img src="https://agentmods.dev/badge/skills/wasintoh/toh-framework/dev-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.03764 |
| Opus 5.5 | $0.00030 | $0.01506 |
| Sonnet 5.5 | $0.00015 | $0.00753 |
| Haiku 4.5 | $0.00007 | $0.00376 |
Grade A, and why
dev-engineer 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 1mo 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 — 592 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Engineer
Add brains to the beauty. Connect logic to UI seamlessly.
<core_principle>
The Enhancement Promise
UI exists (from ui-first-builder) → Add state/logic → UI becomes functional
We don't create UI. We make existing UI work. </core_principle>
<default_to_action> NEVER ask:
- "What state management should I use?" → Use Zustand (our standard)
- "What validation library?" → Use Zod (our standard)
- "What form library?" → Use React Hook Form (our standard)
ALWAYS do:
- When scaffolding a NEW project, run
npm view [package] versionfor each dependency to get the latest STABLE before pinning — check live, never hardcode a version number here (the framework must not go stale; internalize the principle, not the digits) - Create TypeScript types FIRST
- Create Zustand store for state
- Add form validation with Zod
- Prepare CRUD operations (mock first, real later) </default_to_action>
<typescript_patterns>
Type Definitions
Location
Always create: src/types/index.ts or src/types/[feature].ts
Pattern
// src/types/index.ts
// Entity types
export interface User {
id: string
name: string
email: string
role: "admin" | "user" | "editor"
avatar?: string
createdAt: Date
updatedAt: Date
}
export interface Product {
id: string
name: string
description: string
price: number
stock: number
category: string
images: string[]
isActive: boolean
createdAt: Date
updatedAt: Date
}
// Form types (for create/update)
export type CreateProductInput = Omit<Product, "id" | "createdAt" | "updatedAt">
export type UpdateProductInput = Partial<CreateProductInput>
// API response types
export interface PaginatedResponse<T> {
data: T[]
total: number
page: number
pageSize: number
totalPages: number
}
// Common utility types
export type ID = string | number
export type Nullable<T> = T | null
Naming Conventions
- Entity:
User,Product,Order(singular, PascalCase) - Input:
CreateUserInput,UpdateUserInput - Response:
UserResponse,PaginatedResponse<User> - Props:
UserCardProps,ProductListProps</typescript_patterns>
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.
- 1mo ago First seen · 592 lines · 75 tokens per session scan A 80d7c38df4a4
dev-engineer is a skill published in the GitHub repository wasintoh/toh-framework (98 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 3,764 once invoked, about $0.0003 per session on Opus 5.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
ecc-api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Use when designing or reviewing REST endpoints, resource names, status codes, pagination, or versioning.
ecc-api-patterns
FastAPI best practices covering project structure, Pydantic v2 schemas, dependency injection, async handlers, authentication, authorization, transactional service layers, and testing with httpx and pytest. Use when building or reviewing FastAPI apps — Pydantic schemas, dependencies, async handlers, auth, or tests.
document_api
Generates standardized API documentation (OpenAPI/Markdown) for backend endpoints.
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
django-security
Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Use when designing or reviewing REST endpoints, resource names, status codes, pagination, or versioning.