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-discovery/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-discovery)<a href="https://agentmods.dev/skills/takumi0706/google-calendar-mcp/kiro-discovery"><img src="https://agentmods.dev/badge/skills/takumi0706/google-calendar-mcp/kiro-discovery/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-discovery"><img src="https://agentmods.dev/badge/skills/takumi0706/google-calendar-mcp/kiro-discovery.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.00044 | $0.02995 |
| Opus 5 | $0.00022 | $0.01497 |
| Sonnet 5 | $0.00009 | $0.00599 |
| Haiku 4.5 | $0.00004 | $0.00299 |
Grade A, and why
kiro-discovery 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 12d 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
88% identical to kiro-discovery — 68 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kiro-discovery Skill
Core Mission
- Success Criteria:
- Correct action path or work decomposition identified based on existing project state
- User's intent clarified through questions, not assumptions
- Output is an actionable next step (not just a description)
Execution Steps
Step 1: Lightweight Scan
Gather only metadata to determine the action path. Do NOT read full file contents yet.
- Specs inventory: Glob
.kiro/specs/*/spec.json, read each spec.json forname,phasefields andapprovalsstatus. Note feature names and their current status. - Steering existence: Check which files exist in
.kiro/steering/(product.md, tech.md, structure.md, roadmap.md). Do NOT read their contents yet. - Roadmap check: If
.kiro/steering/roadmap.mdexists, read it. This contains project-level context (approach, scope, constraints, spec list) from a previous discovery session. Use it to restore project context. - Top-level structure: List the project root directory to note key directories and files. Do NOT recurse into subdirectories.
This step should consume minimal context. If specs/ is empty and no steering exists, note "greenfield project" and move to Step 2.
Step 2: Determine Action Path
Based on the user's request and the metadata from Step 1, determine which path applies:
Path A: Existing spec covers this
- The request is an extension, enhancement, or fix within an existing spec's domain
- Every meaningful part of the request fits that same spec boundary
- Any remaining small follow-up work can be handled directly without creating a new spec
- Skip remaining steps
Path B: No spec needed
- The request is a bug fix, config change, simple refactor, or trivial addition
- No meaningful part of the request needs a new or updated spec boundary
- The request does not need to update an existing spec either
- Skip remaining steps
Path C: New single-scope feature
- The request is new, doesn't overlap with existing specs, and fits in one spec
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.
- 12d ago First seen · 263 lines · 44 tokens per session scan A 34bc176f9d86
kiro-discovery is a skill published in the GitHub repository takumi0706/google-calendar-mcp (59 stars, last pushed 25d ago), licensed MIT. It adds 44 tokens to every session and 2,995 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to kiro-discovery, differing in 68 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…