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/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/generate-feature)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/generate-feature"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/generate-feature/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/thebeardedbearsas/claude-craft/generate-feature"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/generate-feature.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.00008 | $0.03212 |
| Opus 5.5 | $0.00003 | $0.01285 |
| Sonnet 5.5 | $0.00002 | $0.00642 |
| Haiku 4.5 | $0.00001 | $0.00321 |
Grade A, and why
generate-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 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 — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate C#/.NET Feature
You are a C#/.NET architect. Generate a complete feature following Clean Architecture and CQRS patterns.
Arguments
$ARGUMENTS
FeatureName: Name of the feature to generate (e.g., "Order", "Customer", "Product")
Generation Process
Step 1: Analyze Requirements
Ask if not clear:
- What is the primary entity for this feature?
- What operations are needed? (CRUD, specific business operations)
- What relationships exist with other entities?
- Are there specific validation rules?
Step 2: Generate Domain Layer
Entity:
// Domain/Entities/{Feature}.cs
namespace {Project}.Domain.Entities;
public class {Feature} : BaseEntity, IAggregateRoot
{
private readonly List<{Feature}Item> _items = new();
public string Name { get; private set; } = string.Empty;
public {Feature}Status Status { get; private set; }
public DateTime CreatedAt { get; private set; }
public DateTime? ModifiedAt { get; private set; }
public IReadOnlyCollection<{Feature}Item> Items => _items.AsReadOnly();
private {Feature}() { } // EF Core
public static {Feature} Create(string name)
{
Guard.Against.NullOrWhiteSpace(name, nameof(name));
var entity = new {Feature}
{
Id = Guid.NewGuid(),
Name = name,
Status = {Feature}Status.Draft,
CreatedAt = DateTime.UtcNow
};
entity.AddDomainEvent(new {Feature}CreatedEvent(entity.Id));
return entity;
}
public void UpdateName(string name)
{
Guard.Against.NullOrWhiteSpace(name, nameof(name));
Name = name;
ModifiedAt = DateTime.UtcNow;
AddDomainEvent(new {Feature}UpdatedEvent(Id));
}
public void Activate()
{
if (Status == {Feature}Status.Active)
return;
Status = {Feature}Status.Active;
ModifiedAt = DateTime.UtcNow;
AddDomainEvent(new {Feature}ActivatedEvent(Id));
}
}
Repository Interface:
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 · 482 lines · 8 tokens per session scan A 0804eee0aa57
generate-feature is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 3,212 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
devkit.java.generate-crud
Generates complete CRUD implementation for a Spring Boot domain class using spring-boot-crud-patterns skill. Use when creating new domain entities with REST endpoints.
new-config
Scaffold strongly-typed configuration with IOptions , validation, and environment-specific overrides.
azure-graph-dotnet:add-graph-operation
Add a specific Microsoft Graph operation to an existing C# project — generates a service class, interface, model records, and DI registration for delta scan, metadata PATCH, file moves, or custom Graph calls.
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.