Borrowing it
Nothing to install: this file belongs to gaoconggit/SharpPad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gaoconggit/SharpPad/main/.claude/commands/kiro/steering-custom.mdgit clone --depth 1 https://github.com/gaoconggit/SharpPadWrote 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/gaoconggit/sharppad/steering-custom)<a href="https://agentmods.dev/commands/gaoconggit/sharppad/steering-custom"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/steering-custom/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/gaoconggit/sharppad/steering-custom"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/steering-custom.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.00010 | $0.01403 |
| Opus 5.5 | $0.00004 | $0.00561 |
| Sonnet 5.5 | $0.00002 | $0.00281 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
steering-custom 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 13d 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.
This is a copy
95% identical to steering-custom — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kiro Custom Steering Creation
Create custom steering documents in .kiro/steering/ for specialized contexts beyond the three foundational files (product.md, tech.md, structure.md).
Current Steering Status
Existing Steering Documents
- Core steering files: !
ls -la .kiro/steering/*.md 2>/dev/null || echo "No steering directory found" - Custom steering count: !
if [ -d ".kiro/steering" ]; then count=0; for f in .kiro/steering/*.md; do if [ -f "$f" ] && [ "$f" != ".kiro/steering/product.md" ] && [ "$f" != ".kiro/steering/tech.md" ] && [ "$f" != ".kiro/steering/structure.md" ]; then count=$((count + 1)); fi; done; echo "$count"; else echo "0"; fi
Project Analysis
- Specialized areas: !
find . -path ./node_modules -prune -o -path ./.git -prune -o -type d \( -name "test*" -o -name "spec*" -o -name "api" -o -name "auth" -o -name "security" \) -print 2>/dev/null || echo "No specialized directories found" - Config patterns: !
find . -path ./node_modules -prune -o \( -name "*.config.*" -o -name "*rc.*" -o -name ".*rc" \) -print 2>/dev/null || echo "No config files found"
Task: Create Custom Steering Document
You will create a new custom steering document based on user requirements. Common use cases include:
Common Custom Steering Types
-
API Standards (
api-standards.md)- REST/GraphQL conventions
- Error handling patterns
- Authentication/authorization approaches
- API versioning strategy
-
Testing Approach (
testing.md)- Test file organization
- Naming conventions for tests
- Mocking strategies
- Coverage requirements
- E2E vs unit vs integration testing
-
Code Style Guidelines (
code-style.md)- Language-specific conventions
- Formatting rules beyond linters
- Comment standards
- Function/variable naming patterns
- Code organization principles
-
Security Policies (
security.md)- Input validation requirements
- Authentication patterns
- Secrets management
- OWASP compliance guidelines
- Security review checklist
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.
- 13d ago First seen · 154 lines · 10 tokens per session scan A dab5e0ab536f
steering-custom is a command published in the GitHub repository gaoconggit/SharpPad (83 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 1,403 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to steering-custom, differing in 9 lines, and is treated as a copy.
Other commands, from other repositories
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.
new-bicep-module
Scaffold a new Bicep module with parameters, variables, outputs, tags, and security defaults.
ship-changes
../../.cratis/ai/prompts/ship-changes.prompt.md.
record
Record the browser while validating a flow, then judge it against a rubric.
watch
Open a YouTube URL in your browser so the watcher plugin can auto play/pause it.
security
Scan a .NET project for security vulnerabilities and dependency health issues.