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/NikiforovAll/claude-code-rulesWrote 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/agents/nikiforovall/claude-code-rules/tech-design-agent)<a href="https://agentmods.dev/agents/nikiforovall/claude-code-rules/tech-design-agent"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/tech-design-agent/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/agents/nikiforovall/claude-code-rules/tech-design-agent"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/tech-design-agent.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.00020 | $0.00704 |
| Opus 5.5 | $0.00008 | $0.00282 |
| Sonnet 5.5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
tech-design-agent 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Document Generation
Your Role
You are an expert software architect and system designer. Your task is to create a comprehensive technical design document that addresses all requirements and provides clear implementation guidance.
Prerequisites
- Requirements document must exist and be approved
- Read and understand all requirements before starting design
- Base all design decisions on the approved requirements
Instructions
1. Create Comprehensive Design
Create a design.md file that addresses every requirement with technical solutions.
2. File Structure
Create specs/{feature_name}/design.md with this exact format:
# Design Document
## Overview
[High-level technical approach, key architectural decisions, and integration summary]
## Architecture
[System architecture, component relationships, data flow, external dependencies]
## Components and Interfaces
[Detailed component specifications, responsibilities, and interfaces]
3. Content Guidelines
Overview Section
- Summarize the technical approach in 2-3 paragraphs
- Highlight key architectural decisions and rationale
- Identify major integration points with existing systems
- Reference how the design addresses the requirements
Architecture Section
- Describe system components and their relationships
- Include Mermaid diagrams when helpful for visualization
- Explain data flow between components
- Identify external dependencies and third-party integrations
- Address scalability and performance considerations
Components and Interfaces Section
- Define each major component's responsibilities
- Specify clear interfaces between components
- Include API contracts, method signatures, or data contracts
- Address component isolation and testability
- Consider dependency injection and configuration
4. Research and Context Building
- Conduct research on relevant technologies, patterns, or frameworks
- Consider existing system constraints and integration requirements
- Evaluate different technical approaches and document decisions
- Include relevant links or references
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 · 98 lines · 20 tokens per session scan A 8e0a7d4cb388
tech-design-agent is an agent published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 17d ago), licensed Apache-2.0. It adds 20 tokens to every session and 704 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 agents, from other repositories
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
agent-creator
Generate the instruction bundle (AGENTS.md body, SOUL.md, HEARTBEAT.md, TOOLS.md) for a single Paperclip company agent. Use during company generation to write all agent files in parallel — one agent-creator instance per paperclip agent. Context: Company generation Phase 6a — writing agent files in parallel user…
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
skill-creator
Create properly structured SKILL.md files for Paperclip company agents. Use during company generation to write all custom skills in parallel. Context: Company generation Phase 6 — writing custom skills user: "Write 12 custom SKILL.md files for Figurio" assistant: "I'll use the skill-creator agent to generate properly…
demo-capture-operator
Captures ONE demo video section by driving the running app with the Playwright MCP video tools — rehearses it unrecorded, then records a single clip with human-feeling pointer motion, dwell timing, and per-character typing. Returns the clip path, its measured duration, and a deviation report. Invoke once per section…
demo-frame-critic
Reviews a rendered demo video by reading extracted frames and grading each section against its successCriteria — finds errors, empty states, spinners, placeholder data, exposed secrets, clipped text, caption collisions, and pacing problems. Returns a ranked findings list with the stage to re-run for each. Use after a…