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 timwukp/agent-skills-best-practice --skill kiro-project-setupgit clone --depth 1 https://github.com/timwukp/agent-skills-best-practiceWrote 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/timwukp/agent-skills-best-practice/kiro-project-setup)<a href="https://agentmods.dev/skills/timwukp/agent-skills-best-practice/kiro-project-setup"><img src="https://agentmods.dev/badge/skills/timwukp/agent-skills-best-practice/kiro-project-setup/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/timwukp/agent-skills-best-practice/kiro-project-setup"><img src="https://agentmods.dev/badge/skills/timwukp/agent-skills-best-practice/kiro-project-setup.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.00057 | $0.00737 |
| Opus 5 | $0.00028 | $0.00368 |
| Sonnet 5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
kiro-project-setup 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 10d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kiro Project Setup Skill
Sets up a complete Kiro project structure so your AI assistant understands your project conventions, has access to custom skills, and respects your configuration preferences.
Instructions
When triggered, perform the following steps:
-
Create the
.kiro/steering/directory with aconventions.mdfile containing:- Project naming conventions (file naming, variable naming)
- Code style preferences (formatting, linting rules)
- Architecture patterns used in the project
- Any team-specific rules the user provides
-
Create the
.kiro/skills/directory for project-level skills:- Add a placeholder
SKILL.mdexplaining that project-specific skills live here - These skills are scoped to the repository and not shared globally
- Add a placeholder
-
Add
.gitignoreentries for.kiro/temp files if needed:- If your AI tools create cache or temp files, consider adding entries like
.kiro/cache/or.kiro/tmp/to.gitignore - Keep
.kiro/steering/and.kiro/skills/tracked in version control
- If your AI tools create cache or temp files, consider adding entries like
-
Create a README section (or suggest additions) covering:
- How the project uses Kiro steering files
- Where to find and add project-level skills
- How new team members can customize their setup
Ask the user about their project before generating files. Gather:
- Programming language(s) used
- Preferred code style (tabs vs spaces, naming conventions)
- Any existing linting or formatting tools
- Team size and collaboration patterns
Guidelines
- Always ask before overwriting existing files in
.kiro/ - Keep
conventions.mdconcise and actionable - avoid vague guidance - Use the project's existing style as the basis for conventions when possible
- Suggest committing
.kiro/steering/files so the whole team benefits - Do not add secrets, credentials, or personal preferences to tracked files
- If the project already has a
.kiro/directory, offer to enhance rather than replace
Examples
User says: "Set up Kiro for my TypeScript project"
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.
- 10d ago First seen · 97 lines · 57 tokens per session scan A c5cbd1e5d4c8
kiro-project-setup is a skill published in the GitHub repository timwukp/agent-skills-best-practice (10 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 737 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
ec2
AWS EC2 virtual machine management — instances, security groups, key pairs, AMIs, EBS volumes, Auto Scaling Groups, Spot Instances, Session Manager, placement groups, and instance lifecycle automation. Trigger on ANY of these, even when EC2 isn't named explicitly: - Launching or provisioning: "spin up a server"…
bedrock
AWS Bedrock foundation models for generative AI. Use when invoking foundation models, building AI applications, creating embeddings, configuring model access, or implementing RAG patterns.
cloudformation
AWS CloudFormation infrastructure as code for stack management. Use when writing templates, deploying stacks, managing drift, troubleshooting deployments, or organizing infrastructure with nested stacks.
cloudwatch
AWS CloudWatch monitoring for logs, metrics, alarms, and dashboards. Use when setting up monitoring, creating alarms, querying logs with Insights, configuring metric filters, building dashboards, or troubleshooting application issues.
dynamodb
AWS DynamoDB NoSQL database for scalable data storage. Use when designing table schemas, writing queries, configuring indexes, managing capacity, implementing single-table design, or troubleshooting performance issues.
ecs
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.