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 commands/ruslan-korneev/claude-plugins/dtogit clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWrote 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/commands/ruslan-korneev/claude-plugins/dto)<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/dto"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/dto.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 | $0.00012 | $0.01276 |
| Opus 5 | $0.00006 | $0.00638 |
| Sonnet 5 | $0.00002 | $0.00255 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
dto 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 3d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command /fastapi:dto
Create Pydantic DTOs (Create, Read, Update) based on SQLAlchemy model.
Instructions
Step 1: Read model
Find and read SQLAlchemy model:
# If path is provided
cat {{ model }}
# If name is provided
grep -r "class {{ model }}" src/
Step 2: Extract fields
Determine:
- All model fields
- Field types
- Nullable fields
- Fields with default values
- Relationships
Step 3: Create DTOs
SQLAlchemy → Pydantic Type Mapping
| SQLAlchemy | Pydantic |
|---|---|
Integer |
int |
String |
str |
Boolean |
bool |
Float |
float |
DateTime |
datetime |
Date |
date |
Text |
str |
JSON |
dict or list |
Enum |
Literal[...] or Enum |
UUID |
uuid.UUID |
BaseDTO
"""{{ model }} DTOs."""
from datetime import datetime
from pydantic import BaseModel, ConfigDict, Field
class {{ model }}BaseDTO(BaseModel):
"""Base DTO with common configuration."""
model_config = ConfigDict(
from_attributes=True,
populate_by_name=True,
str_strip_whitespace=True,
)
CreateDTO
class {{ model }}CreateDTO({{ model }}BaseDTO):
"""DTO for creating {{ model }}.
Excludes: id, created_at, updated_at (auto-generated).
"""
# Required fields (without default)
name: str = Field(..., min_length=1, max_length=255)
email: str = Field(..., pattern=r"^[\w\.-]+@[\w\.-]+\.\w+$")
# Optional fields
description: str | None = None
is_active: bool = True
ReadDTO
class {{ model }}ReadDTO({{ model }}BaseDTO):
"""DTO for reading {{ model }}.
Includes all fields including auto-generated.
"""
id: int
name: str
email: str
description: str | None
is_active: bool
created_at: datetime
updated_at: datetime | None
UpdateDTO
class {{ model }}UpdateDTO(BaseModel):
"""DTO for updating {{ model }}.
All fields are optional.
"""
model_config = ConfigDict(from_attributes=True)
name: str | None = Field(None, min_length=1, max_length=255)
email: str | None = Field(None, pattern=r"^[\w\.-]+@[\w\.-]+\.\w+$")
description: str | None = None
is_active: bool | None = None
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.
- 3d ago First seen · 252 lines · 12 tokens per session scan A 10c394b307b1
dto is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 1,276 once invoked, about $0.0001 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 commands, from other repositories
sync
Sync the audit manifest with Azure DevOps work items — set the connector up for the first time (connect: verify the transport, report which auth path is in effect, prove access read-only, detect the board's process), push manifest bugs/tasks/phases to ADO (board states, sprint stamp, Remaining Work, comments), pull…
init
Multi-agent codebase audit that GENERATES the audit manifest (phases/tasks) at manifestPath. Interviews you for scope/goals, fans out parallel read-only explorers, synthesizes findings, then presents the proposed phases for approval BEFORE writing — approve to materialize, or park them as proposals for later…
task
Add a tracked task to the audit manifest — every answer is a flag, and the dialogue only covers what the caller did not pass — move one between phases, or cancel work that will not be done. add allocates the id, initializes all orchestrator fields, updates fileIndex, and revalidates; move renumbers a task into another…
panel
Audit pipeline: open / stop / check a local control-panel UI to visually manage .claude/audit.config.json and the manifest's composition levers (reviewSkill, per-task skills/models, buildCommands) — with live validation and discovery of the skills & agents available in this repo + globally. Ephemeral, on-demand; a…
doctor
Audit pipeline: diagnose the setup before it bites — interpreter the hooks will use, git root, config, manifest + shard integrity, which plan-gate tier is active, submodule conflicts, build runners, whether hooks have ever fired and which copy of the plugin ran them, the usage ledger, whether the audit trail still…
status
Audit pipeline: print manifest status — phases, tasks, bugs, the ready-now list and what each pending task is waiting on; or, with --gate, turn that same state into a CI pass/fail verdict over conditions you pick with --fail-on. Read-only, no locks, no mutations.