Borrowing it
Nothing to install: this file belongs to takumi0706/google-calendar-mcp. 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/takumi0706/google-calendar-mcp/main/.claude/skills/kiro-steering-custom/SKILL.mdgit clone --depth 1 https://github.com/takumi0706/google-calendar-mcpWrote 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/takumi0706/google-calendar-mcp/kiro-steering-custom)<a href="https://agentmods.dev/skills/takumi0706/google-calendar-mcp/kiro-steering-custom"><img src="https://agentmods.dev/badge/skills/takumi0706/google-calendar-mcp/kiro-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/skills/takumi0706/google-calendar-mcp/kiro-steering-custom"><img src="https://agentmods.dev/badge/skills/takumi0706/google-calendar-mcp/kiro-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.00023 | $0.01096 |
| Opus 5 | $0.00012 | $0.00548 |
| Sonnet 5 | $0.00005 | $0.00219 |
| Haiku 4.5 | $0.00002 | $0.00110 |
Grade A, and why
kiro-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 kiro-steering-custom — 44 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kiro-steering-custom Skill
Role
You are a specialized skill for creating custom steering documents beyond core files (product, tech, structure).
Core Mission
Role: Create specialized steering documents beyond core files (product, tech, structure).
Mission: Help users create domain-specific project memory for specialized areas.
Success Criteria:
- Custom steering captures specialized patterns
- Follows same granularity principles as core steering
- Provides clear value for specific domain
Execution Steps
Step 1: Gather Context
If steering context is already available from conversation, skip redundant file reads. Otherwise:
- Check
.kiro/settings/templates/steering-custom/for available templates - Read
rules/steering-principles.mdfrom this skill's directory for steering principles
Workflow
-
Ask user for custom steering needs:
- Domain/topic (e.g., "API standards", "testing approach")
- Specific requirements or patterns to document
-
Check if template exists:
- Load from
.kiro/settings/templates/steering-custom/{name}.mdif available - Use as starting point, customize based on project
- Load from
-
Analyze codebase (JIT) for relevant patterns:
Parallel Research
The following research areas are independent and can be executed in parallel:
- Template & principles: Load matching template and steering-principles.md
- Domain patterns: Analyze codebase for domain-specific patterns using Glob/Grep/Read
After all parallel research completes, synthesize findings for steering document.
-
Generate custom steering:
- Follow template structure if available
- Apply principles from
rules/steering-principles.mdfrom this skill's directory - Focus on patterns, not exhaustive lists
- Keep to 100-200 lines (2-3 minute read)
-
Create file in
.kiro/steering/{name}.md
Available Templates
Templates available in .kiro/settings/templates/steering-custom/:
- api-standards.md - REST/GraphQL conventions, error handling
- testing.md - Test organization, mocking, coverage
- security.md - Auth patterns, input validation, secrets
- database.md - Schema design, migrations, query patterns
- error-handling.md - Error types, logging, retry strategies
- authentication.md - Auth flows, permissions, session management
- deployment.md - CI/CD, environments, rollback procedures
What ships with it
1 file 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.
- 13d ago First seen · 144 lines · 23 tokens per session scan A 83d656b428f0
kiro-steering-custom is a skill published in the GitHub repository takumi0706/google-calendar-mcp (59 stars, last pushed 25d ago), licensed MIT. It adds 23 tokens to every session and 1,096 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to kiro-steering-custom, differing in 44 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…