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 dean0x/devflow --skill consistencygit clone --depth 1 https://github.com/dean0x/devflowWrote 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/dean0x/devflow/consistency)<a href="https://agentmods.dev/skills/dean0x/devflow/consistency"><img src="https://agentmods.dev/badge/skills/dean0x/devflow/consistency/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/dean0x/devflow/consistency"><img src="https://agentmods.dev/badge/skills/dean0x/devflow/consistency.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.00018 | $0.00912 |
| Opus 5.5 | $0.00007 | $0.00365 |
| Sonnet 5.5 | $0.00004 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
consistency 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 7d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consistency Patterns
Domain expertise for code consistency and unnecessary simplification detection. Use alongside devflow:review-methodology for complete consistency reviews.
Iron Law
MATCH EXISTING PATTERNS OR JUSTIFY DEVIATION
New code should look like existing code. If the codebase uses camelCase, use camelCase. If errors return Result types, return Result types. Consistency trumps personal preference. Deviation requires explicit justification and team agreement. One codebase, one style.
Consistency Categories
1. Unnecessary Simplification
Content truncation, stripped configuration, removed error context.
// VIOLATION: Oversimplified error messages
const errorMessages = {
INVALID_EMAIL: 'Invalid email', // Was: detailed format guidance
USER_NOT_FOUND: 'Not found', // Was: helpful next steps
};
// CORRECT: Preserve helpful context
const errorMessages = {
INVALID_EMAIL: 'Please enter a valid email address in the format [email protected]',
USER_NOT_FOUND: 'We could not find an account with that email. Please check or create a new account.',
};
2. Pattern Violations
Naming conventions, error handling styles, import/export organization.
// EXISTING PATTERN: Result types
function existingFunction(): Result<User, Error> {
if (!valid) return Err(new ValidationError('...'));
return Ok(user);
}
// VIOLATION: Throws instead of Result
function newFunction(): User {
if (!valid) throw new Error('...'); // Different pattern!
return user;
}
// CORRECT: Match existing
function newFunction(): Result<User, Error> {
if (!valid) return Err(new ValidationError('...'));
return Ok(user);
}
3. Feature Regression
Removed CLI options, changed return types, removed event emissions.
// VIOLATION: Removed event emissions break listeners
class OrderService {
async createOrder(data: OrderData) {
const order = await this.repository.create(data);
return order; // Events removed - listeners won't fire!
}
}
// CORRECT: Preserve all event emissions
class OrderService {
async createOrder(data: OrderData) {
const order = await this.repository.create(data);
this.events.emit('order.created', order);
this.events.emit('inventory.reserve', order.items);
return order;
}
}
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago Changed · -6 tokens per session 3a6cc08c518c
- 1mo ago First seen · 141 lines · 24 tokens per session scan A ec7c751f3423
consistency is a skill published in the GitHub repository dean0x/devflow (20 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 912 once invoked, about $0.0001 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
argot-suggest-rules
Turn a convention argot has already discovered into a scripted custom rule. Runs argot conventions, surfaces the repo's mined placement conventions (where a kind of code lives — "validation in schema files", "DB access only in migrations", "business logic in the service layer, not views") and internal-API vocabulary…
software-design-patterns-and-refactoring
Use when architecture or backend work needs pre-code structural guidance from design patterns, or post-code cleanup guidance from refactoring and code-smell-driven improvement.
api-contract-audit
Static OpenAPI contract audit - endpoint drift (spec vs code), schema drift, status-code mismatch, breaking-change detection vs previous spec version, versioning consistency, security scheme alignment, deprecation markers, Richardson Maturity L0-L3 scoring. Framework auto-gen for FastAPI, NestJS…
microservices-architecture
Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.
gate-design
Review technical design documents for API contracts, data models, component architecture, and technology decisions.
architect-review
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.