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.
git clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/srnichols/plan-forge/new-dto)<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-dto"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-dto/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/commands/srnichols/plan-forge/new-dto"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-dto.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.00019 | $0.00620 |
| Opus 5 | $0.00010 | $0.00310 |
| Sonnet 5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
new-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 today.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New DTO (Data Transfer Object)
Scaffold request and response DTOs that separate API contracts from domain entities.
Required Pattern
Response DTO
// Immutable record — returned from API endpoints
public record {EntityName}Dto(
Guid Id,
string Name,
string Description,
DateTime CreatedAt,
DateTime UpdatedAt);
Create Request DTO
// Input validation via DataAnnotations or FluentValidation
public record Create{EntityName}Request(
[Required, StringLength(200, MinimumLength = 1)]
string Name,
[StringLength(2000)]
string? Description);
Update Request DTO
public record Update{EntityName}Request(
[Required, StringLength(200, MinimumLength = 1)]
string Name,
[StringLength(2000)]
string? Description);
FluentValidation (Complex Rules)
public class Create{EntityName}RequestValidator : AbstractValidator<Create{EntityName}Request>
{
public Create{EntityName}RequestValidator()
{
RuleFor(x => x.Name)
.NotEmpty()
.MaximumLength(200);
RuleFor(x => x.Description)
.MaximumLength(2000)
.When(x => x.Description is not null);
}
}
Mapping (Manual or AutoMapper)
// Prefer manual mapping for simple cases — explicit and debuggable
public static {EntityName}Dto ToDto(this {EntityName} entity) =>
new(entity.Id, entity.Name, entity.Description, entity.CreatedAt, entity.UpdatedAt);
public static {EntityName} ToEntity(this Create{EntityName}Request request) =>
new() { Name = request.Name, Description = request.Description };
Paged Response Wrapper
public record PagedResult<T>(
IReadOnlyList<T> Items,
int Page,
int PageSize,
int TotalCount)
{
public int TotalPages => (int)Math.Ceiling((double)TotalCount / PageSize);
public bool HasNext => Page < TotalPages;
public bool HasPrevious => Page > 1;
}
Rules
- NEVER return domain entities directly from API endpoints
- NEVER accept domain entities as input — always use request DTOs
- Use
recordtypes for immutability - Validate at the boundary using DataAnnotations or FluentValidation
- Keep DTOs in a separate
Models/orContracts/folder - Map explicitly — avoid magic mapping for critical paths
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.
- today First seen · 98 lines · 19 tokens per session scan A 4f24714bb3e2
new-dto is a command published in the GitHub repository srnichols/plan-forge (5 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 620 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-09-08.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.