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 ihatesea69/kiro-kit --skill researchgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/research)<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/research"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/research/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/ihatesea69/kiro-kit/research"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/research.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.00027 | $0.00213 |
| Opus 5.5 | $0.00011 | $0.00085 |
| Sonnet 5.5 | $0.00005 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
research 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.
What it actually says
Research
Activate this skill when evaluating technologies, comparing libraries, or investigating best practices.
When to Use
- Evaluating competing libraries or frameworks
- Investigating best practices for a specific domain
- Comparing architectural approaches
- Assessing security implications of a technology choice
- Understanding unfamiliar APIs or protocols
Process
- Define the research question precisely
- Identify authoritative sources (official docs, RFCs, benchmarks)
- Gather data from multiple sources
- Cross-reference and validate findings
- Evaluate trade-offs in context of the project
- Produce actionable recommendation with confidence level
Rules
- Prioritize official documentation over blog posts
- Note version numbers and compatibility requirements
- Distinguish proven patterns from experimental approaches
- State confidence level for each recommendation
- Flag when information may be outdated
- Include maintenance status and community health of libraries
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 · 35 lines · 27 tokens per session scan A ab627bfd6aa4
research is a skill published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 213 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-09-03.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…