agentmods.dev

find-decisions

find-decisions is a skill for Claude Code from DavidROliverBA/ArchitectKB. It costs 0 tokens per session (522 once invoked), scanned A, original, MIT.

A search workflow that finds architecture decisions—documented choices about how a software system should be built—across project notes and technical documents.

In plain words
What is it for?
Use it to look for decisions about topics such as Kafka, authentication, or integrations across architecture records, meeting notes, project files, and technical documentation.
Why use it?
It reduces the need to search many files manually when you need to understand why a system was designed a certain way.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter. Also seen: mentions subagents.

not rated 52repo 6mo ago A scan 0 tokens original MIT

Good fit Use it to look for decisions about topics such as Kafka, authentication, or integrations across architecture records, meeting notes, project files, and technical documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davidroliverba/architectkb/find-decisions
View source ↗ DavidROliverBA/ArchitectKB
Install

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.

Any agent
npx skills add DavidROliverBA/ArchitectKB --skill find-decisions
Clone the repo
git clone --depth 1 https://github.com/DavidROliverBA/ArchitectKB

Made for: Claude Code.

Wrote 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.

agentmods badge for find-decisions

README.md
[![agentmods](https://agentmods.dev/badge/skills/davidroliverba/architectkb/find-decisions.svg)](https://agentmods.dev/skills/davidroliverba/architectkb/find-decisions)
Your own site
<a href="https://agentmods.dev/skills/davidroliverba/architectkb/find-decisions"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/find-decisions.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 522 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00522
Opus 5 $0.00000 $0.00261
Sonnet 5 $0.00000 $0.00104
Haiku 4.5 $0.00000 $0.00052

Measured 8d ago against content hash 954b424c583e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

find-decisions 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 8d 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.

.claude/skills/find-decisions/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/find-decisions

Find all architecture decisions and choices related to a topic using sub-agents.

Usage

/find-decisions <topic>
/find-decisions Kafka
/find-decisions authentication
/find-decisions SAP integration

Instructions

Phase 1: Planning

  1. Identify search terms from the topic
  2. Plan search across multiple note types:
    • ADRs (primary source)
    • Meeting notes (decisions made sections)
    • Project files (architectural notes)
    • Pages (technical documentation)

Phase 2: Parallel Search (use sub-agents)

Launch these sub-agents in parallel using model: "haiku" for efficiency:

Agent 1: ADR Search (Haiku)

  • Search all ADR - *.md files
  • Look for topic in title, context, decision sections
  • Extract: title, status, decision summary, date

Agent 2: Meeting Decisions (Haiku)

  • Search +Meetings/Meeting - *.md files
  • Focus on "Decisions Made" and "Action Items" sections
  • Look for topic keywords
  • Extract: date, meeting name, decision text

Agent 3: Technical Documentation (Haiku)

  • Search Page - *.md files
  • Look for architectural/technical content about topic
  • Extract relevant sections

Agent 4: Project References (Haiku)

  • Search Project - *.md files
  • Find projects that involve this topic
  • Note any architectural decisions mentioned

Phase 3: Compile Results

# Decisions Related to: {{topic}}

**Search Date**: {{DATE}}
**Results Found**: {{count}}

## Architecture Decision Records

| ADR | Status | Decision | Date |
|-----|--------|----------|------|
{{ADR results}}

### ADR Details

#### {{ADR Title}}
- **Status**: {{status}}
- **Decision**: {{summary}}
- **Rationale**: {{key points}}
- **Link**: [[ADR - {{title}}]]

## Decisions from Meetings

| Date | Meeting | Decision |
|------|---------|----------|
{{meeting decisions}}

## Related Projects

{{projects involving this topic}}

## Technical Documentation

{{relevant pages with summaries}}

## Timeline

{{chronological view of decisions}}

## Gaps Identified

{{note if there are areas without documented decisions}}

Read the full file on GitHub · 100 lines

Changes

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.

  1. 8d ago First seen · 100 lines · 0 tokens per session scan A 954b424c583e

Subscribe to this mod's changes

find-decisions is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 522 tokens. 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-30.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens