search-content

search-content is a skill for Claude Code, Codex from legacybridge-tech/claude-plugins. It costs 48 tokens per session (3,315 once invoked), scanned A, original, MIT.

A search and navigation helper for a knowledge base made up of files and folders. It uses README.md indexes, filename and content matching, and directory structure to locate information.

In plain words
What is it for?
Use it to find files, notes, topics, content locations, or groups of documents such as research notes or meeting records.
Why use it?
It removes the need to search folders manually or remember where notes are stored. It can narrow searches by topic, directory, category, or date when the request provides those details.

Skill for Claude CodeCodex

Part of the akashicrecords plugin — 7 skills, 2 commands, 1 agent shipped together

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.

agentmods
npx agentmods add skills/legacybridge-tech/claude-plugins/search-content
Any agent
npx skills add legacybridge-tech/claude-plugins --skill search-content
Clone the repo
git clone --depth 1 https://github.com/legacybridge-tech/claude-plugins

Made for: Claude Code, Codex.

Or install akashicrecords, the plugin that ships this one along with the rest of its 7 skills, 2 commands, 1 agent.

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 search-content

README.md
[![agentmods](https://agentmods.dev/badge/skills/legacybridge-tech/claude-plugins/search-content.svg)](https://agentmods.dev/skills/legacybridge-tech/claude-plugins/search-content)
Your own site
<a href="https://agentmods.dev/skills/legacybridge-tech/claude-plugins/search-content"><img src="https://agentmods.dev/badge/skills/legacybridge-tech/claude-plugins/search-content.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,315 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00048 $0.03315
Opus 5 $0.00024 $0.01657
Sonnet 5 $0.00010 $0.00663
Haiku 4.5 $0.00005 $0.00331

Measured 5d ago against content hash 9e2d9f7ed685, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

search-content 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 5d 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.

akashicrecords/skills/search-content/SKILL.md · 531 lines

How it starts

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

Search Content Skill

Navigate and search the knowledge base efficiently using AkashicRecords directory governance structure.

When to use this Skill

  • User asks "where is", "find", "search for"
  • User queries file locations
  • User looks for specific topics or content
  • User needs to navigate knowledge base
  • User asks "do I have notes about..."

Workflow

1. Analyze Query

Parse user request:

  • Extract keywords and topics
  • Identify search scope (specific directory or entire knowledge base)
  • Determine search type (filename, content, topic, date-based)
  • Assess query specificity (exact match vs fuzzy search)

Examples:

"Where are my transformer notes?" → Topic search, keyword: "transformer"
"Find files modified last week" → Date-based search
"Search for 'attention mechanism' in Research" → Content search, scoped to Research/
"List all meeting notes from October" → Category + date search

2. Choose Search Strategy

Select appropriate strategy based on query:

Strategy 1: Structured Navigation (Preferred)

When to use:

  • Query mentions directory names (Work, Research, Personal, etc.)
  • Looking for specific categories or types
  • Query has clear organizational clues

Method:

  • Start at root README.md or specified directory
  • Follow directory index structure
  • Use README.md files as curated navigation guides
  • Narrow down systematically

Advantages:

  • Fast and efficient
  • Leverages existing organization
  • Follows curated structure
Strategy 2: Pattern Search

When to use:

  • Looking for filenames matching patterns
  • User provides specific naming clues
  • Need to find files by naming convention

Method:

  • Use Glob for filename patterns: **/*keyword*.md
  • Filter by date if needed: files modified in last N days
  • Use multiple patterns for comprehensive search

Advantages:

  • Direct filename matching
  • Fast for filename-based queries
  • Good for date-based searches
Strategy 3: Deep Content Search

When to use:

  • Looking for specific text or code within files
  • Pattern/structured search insufficient
  • Need comprehensive text search

Read the full file on GitHub · 531 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. 5d ago First seen · 531 lines · 48 tokens per session scan A 9e2d9f7ed685

Subscribe to this mod's changes

search-content is a skill published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 3,315 once invoked, about $0.0002 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.

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

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

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens