agentsclimarketplace

Engineering

97,255 rows, by stacks then stars

  • Setup

    techwolf-ai/ai-first-toolkit/plugins/people-management/skills/setup Skill

    145★ repo

    Interactive onboarding that discovers team structure, terminology, development goals, performance and management frameworks, organizational values, and ways of working by crawling Slack, Notion, Google Drive, Gmail, and Calendar. Validates everything with the manager before persisting. Run this first before using any other skill. Also handles periodic context refreshes via /setup --refresh.

  • Triage messages

    techwolf-ai/ai-first-toolkit/plugins/people-management/skills/triage-messages Skill

    145★ repo

    Batch-processes Slack messages and emails to surface what needs the manager's attention, categorised by urgency and type. Designed for batch-responder managers who do Slack sweeps rather than staying in reactive mode. Supports effective communication and responsiveness. Never drafts replies, only surfaces and prioritises.

  • Goal prompt

    techwolf-ai/ai-first-toolkit/plugins/session-tools/skills/goal-prompt Skill

    145★ repo

    Turn a task, plan, or feature request into a ready-to-paste Claude Code /goal command — a single completion condition with a measurable end state, a demonstrable proof, and the constraints that must not drift. Use when the user says "give me a goal", "goal prompt", "make this a /goal", "turn this into a goal", or wants an autonomous long-running objective for Claude Code.

  • Handoff

    techwolf-ai/ai-first-toolkit/plugins/session-tools/skills/handoff Skill

    145★ repo

    Write a session handoff at the end of a session so the next session can start from where this one stopped without rereading the whole conversation. Use when user says "handoff", "wrap up", "write a handoff", "end of session", "park this session", "save where we are", or to RESUME with "/handoff read", "pick up the handoff", "read the handoff". Writes a tight resume note (HANDOFF.md) into the working directory, not a full transcript. Scope is the current project's resume note only: not searching or summarizing past sessions, and not any project-specific "resume" command the environment may have.

  • Build mcp

    techwolf-ai/ai-first-toolkit/plugins/tool-build-kit/skills/build-mcp Skill

    145★ repo

    Build an MCP server end to end, tailored to how it will be used. Use when asked to build an MCP, create an MCP server, wrap an API as a tool, make a tool for Claude, expose a service to an agent, build a Claude connector, or turn a service into MCP tools. Asks up front who the server is for (just me, my org, or public) and what it wraps, then walks through analyze, build, deploy, scale, and distribute with steps tailored to that answer. Builds on the example-skills:mcp-builder skill for implementation depth.

  • Build plugin

    techwolf-ai/ai-first-toolkit/plugins/tool-build-kit/skills/build-plugin Skill

    145★ repo

    Bundle skills, hooks, agents, or an MCP server into one installable Claude Code plugin and ship it. Use when asked to bundle tools into one plugin, package tools for a colleague, publish a plugin to a marketplace, share my tools with my team, or ship a plugin. Asks who it's for and where it's hosted, then walks analyze, assemble, ship, and maintain, tailored to that answer. Sibling to build-mcp.

  • Committer onboarding

    apache/magpie/skills/committer-onboarding Skill

    145★ repo

    Post-vote committer and PMC onboarding for Apache projects. Walks the nominator through every step from ICLA check to welcome announcement for both incubating podlings and graduated top-level projects.

  • Flaky test triage

    apache/magpie/skills/flaky-test-triage Skill

    145★ repo

    Read-only flaky-test detection from GitHub Actions CI run history for one repository. Parses workflow run outcomes over a configurable window, computes per-job failure rates, and distinguishes intermittent failures (flaky) from consistent failures (deterministically broken). Produces a prioritised triage list without modifying any test code, workflow file, or tracker state.

  • Issue fix workflow

    apache/magpie/skills/issue-fix-workflow Skill

    145★ repo

    For a single triaged `<issue-tracker>` issue confirmed as a bug or feature, draft a fix against `<upstream>` on `<default-branch>`. Produces the failing test, the smallest production change, the targeted+module test runs, and the commit. The PR is NOT opened on autopilot; the human committer reviews, signs, and pushes. Hand-back artefact summarises branch, commits, test results, and scope.

  • Issue triage

    apache/magpie/skills/issue-triage Skill

    145★ repo

    For each open `<issue-tracker>` issue in the configured candidate pool, read the issue body and comments and classify the candidate disposition. On user confirmation, posts a triage-proposal comment that invites the project team to react. Read-only on tracker state — no workflow transitions, closures, or label changes. Six classes in the body.

  • Onboarding concierge

    apache/magpie/skills/onboarding-concierge Skill

    145★ repo

    Answer a newcomer's "how do I contribute here" question by grounding the response in `CONTRIBUTING.md` and the project's own docs. Classifies the question (setup / workflow / first-issue / out-of-scope), retrieves the relevant guide excerpt, and drafts a concise answer in the Agentic Mentoring teaching register. Routes out-of-scope questions (design, security, deprecation, architectural taste) to a human maintainer. Read-only; produces a draft answer text — no files are written and no comments are posted without the maintainer's explicit action.

  • Optimize skill

    apache/magpie/skills/optimize-skill Skill

    145★ repo

    Optimize an existing framework skill (or sweep a set of them) by applying the restructuring patterns proven on the security-skill suite: split an oversized `SKILL.md` into linked sibling docs, lift concrete/project-specific values out of the body into `<project-config>` placeholders, replace in-agent-context body reads with out-of-context tool calls, batch per-item fetches into a single upfront pass, and add a deterministic pre-flight no-op classifier ahead of LLM passes. Every change is a behavior- preserving proposal the maintainer signs off on; the skill validator must stay green before and after. The refactoring sibling of `write-skill` (which authors net-new skills).

  • Pairing multi agent review

    apache/magpie/skills/pairing-multi-agent-review Skill

    145★ repo

    Fan a local diff through three independent, axis-focused review passes (correctness, security, conventions), then merge the findings into a single structured report. Each pass is isolated so findings from one axis cannot suppress or bias the others. The merged report uses the same format as pairing-self-review so the developer gets a consistent signal regardless of which Agentic Pairing skill they invoke.

  • Pr management triage

    apache/magpie/skills/pr-management-triage Skill

    145★ repo

    Sweep open pull requests on the configured `<upstream>` repo, classify each one against the project's quality criteria, propose a disposition, and — on the maintainer's confirmation — carry out the action via `gh`. Disposition options per PR: draft / comment / close / rebase / CI-rerun / workflow-approve / ping-stale-reviewer / request author confirmation of readiness / mark `ready for maintainer review` / promote bot-authored draft. Does **not** perform code review — that lives in `pr-management-code-review`.

  • Release announce draft

    apache/magpie/skills/release-announce-draft Skill

    145★ repo

    Draft the `[ANNOUNCE]` email body and open (not merge) the site-bump PR for a promoted release of `<upstream>`. Reads release metadata from the planning issue and `<project-config>/release-management-config.md`; produces a ready-to-copy `[ANNOUNCE]` subject + body and proposes the site-bump PR. Never sends mail and never merges the PR without explicit RM confirmation.

  • Release archive sweep

    apache/magpie/skills/release-archive-sweep Skill

    145★ repo

    Scan the release distribution area (`dist/release/<project>/` when `release_dist_backend = svnpubsub`, or the configured distribution location), identify releases past the project's retention rule, and propose the backend-shaped command set to move them to the archive area. Read-only on the distribution surface; the RM executes every archival command as themselves.

  • Release audit report

    apache/magpie/skills/release-audit-report Skill

    145★ repo

    Assemble a per-release audit record from lifecycle artefacts (planning issue, vote thread, artefact list, promote revision, and announcement URL) and propose a PR appending it to the project's audit log. Read-only on every release surface; the only write is a PR the RM reviews and a committer merges.

  • Release keys sync

    apache/magpie/skills/release-keys-sync Skill

    145★ repo

    Draft the diff that adds the Release Manager's public key to the project's KEYS file (`<keys-file-url>`), emit a paste-ready `svn` (or backend-equivalent) command sequence, remind the RM to upload to the configured keyserver, and validate the key meets the ASF strength floor. Never commits, never holds or reads the private key. Runs during release preparation, before RC signing begins.

  • Release prepare

    apache/magpie/skills/release-prepare Skill

    145★ repo

    Draft release preparation artefacts for `<upstream>`: the planning issue, the version-bump and changelog prep PR, or the post-release development-version bump PR. Reads release metadata from `<project-config>/release-trains.md` and `<project-config>/release-management-config.md`. Every output is a draft confirmed by the Release Manager before filing; the agent never marks a PR ready, never merges, and never closes any artefact.

  • Release promote

    apache/magpie/skills/release-promote Skill

    145★ repo

    Emit the backend-shaped promotion command set for a release that has passed its vote. Reads the planning issue (must carry `vote-passed`), constructs the staging → release move for the configured distribution backend, checks PMC membership of the Release Manager, and proposes the `promoted` label. Never runs the promotion command itself and never publishes the release.

  • Release rc cut

    apache/magpie/skills/release-rc-cut Skill

    145★ repo

    Emit the paste-ready command sequence to tag an RC, build artefacts, sign each artefact, generate checksums, and stage them to the adopter's distribution backend. Covers Steps 4–5 of the release-management lifecycle. Never runs any command locally — all sequences are emitted for the Release Manager to execute on their own machine with their own key and ASF credentials.

  • Release verify rc

    apache/magpie/skills/release-verify-rc Skill

    145★ repo

    Read-only pre-flight verification of a staged release candidate (RC) for `<upstream>`. Checks artefact integrity (GPG signatures and checksums), Apache RAT licence headers, NOTICE/LICENSE completeness, prohibited-binary absence (including `.pyc` / `__pycache__`), source-tree integrity (no dangling symlinks or broken internal references), and version-string consistency. Emits a structured PASS / PASS-WITH-WARNINGS / FAIL report. Makes no state change; a `--post-to <planning-issue>` flag proposes a comment for explicit RM confirmation before any posting.

  • Release vote draft

    apache/magpie/skills/release-vote-draft Skill

    145★ repo

    Draft the `[VOTE]` email body and planning-issue comment for an RC of `<upstream>`. Reads RC metadata from the planning issue and `<project-config>/release-management-config.md`; produces a ready-to-copy `[VOTE]` subject + body and a proposed planning-issue comment. Never sends mail and never posts without explicit RM confirmation.

  • Release vote tally

    apache/magpie/skills/release-vote-tally Skill

    145★ repo

    After the approval window closes, fetch the approval signal for an RC of `<upstream>`, classify each reply as +1 / 0 / -1 and binding or non-binding against the configured roster, produce the tally summary, and draft the `[RESULT] [VOTE]` email. Never sends mail and never applies a label without explicit RM confirmation.

  • Security cve allocate

    apache/magpie/skills/security-cve-allocate Skill

    145★ repo

    Walk a security team member through allocating a CVE for an `<tracker>` tracking issue (governance-gated per `governance.cve_allocation_gate`). Prints the configured `<cve-tool>` allocation URL, waits for the allocated CVE ID, then updates the tracker in place. Tracker updates: CVE tool link field, cve allocated label, status-change comment, CVE JSON. Chains into `security-issue-sync` afterwards to reconcile the rest of the tracker.

  • Security issue deduplicate

    apache/magpie/skills/security-issue-deduplicate Skill

    145★ repo

    Merge two <tracker> tracking issues that describe the same root-cause vulnerability, preserving every reporter's credit, every mailing-list thread reference, and every independent attack-vector description. Updates the kept issue's body in place, closes the duplicate with the `duplicate` label, and regenerates the CVE JSON attachment so both finders land in `credits[]`.

  • Security issue fix

    apache/magpie/skills/security-issue-fix Skill

    145★ repo

    Attempt to fix a security issue tracked in `<tracker>` by implementing the change in a public `<upstream>` PR. Runs `security-issue-sync` first to reconcile the issue's state, proposes an implementation plan, and on explicit user confirmation writes the change, opens a PR from the user's fork, and updates the `<tracker>` tracking issue. Public PR content is scrubbed so it does **not** reveal the CVE, the security nature of the change, or any link back to `<tracker>`.

  • Security issue import from md

    apache/magpie/skills/security-issue-import-from-md Skill

    145★ repo

    Open one or more `<tracker>` tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the `Needs triage` board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

  • Security issue import from pr

    apache/magpie/skills/security-issue-import-from-pr Skill

    145★ repo

    Open a tracking issue in <tracker> for a security-relevant fix that has already been opened (or merged) as a public PR in <upstream>, in the case where there is no inbound `<security-list>` report. The tracker lands in the `Assessed` board column with the scope label applied, `pr created` / `pr merged` reflecting the PR's state, and `Remediation developer` / `PR with the fix` body fields populated from the PR. Pairs with `security-cve-allocate` afterwards.

  • Security issue import from scan

    apache/magpie/skills/security-issue-import-from-scan Skill

    145★ repo

    Triage a security scanner's multi-finding output (read via a pluggable scan-format adapter) and turn findings into security work only after a complete operator-reviewed triage. Reads the scan's finding index plus its per-finding evidence; buckets each finding by disposition; applies only the operator's confirmed per-entry decisions. Publishes the report as a gist and can open a report-back PR.

  • Security issue import via forwarder

    apache/magpie/skills/security-issue-import-via-forwarder Skill

    145★ repo

    Optional sub-skill of `security-issue-import`, `security-issue-invalidate`, and `security-issue-sync` that handles the *relay/forwarder* case: a report that did not arrive directly from the reporter but was relayed onto `<security-list>` by an upstream broker (the ASF security team, a third-party disclosure platform, or an internal SOC). Runs after the parent skill's generic classification cascade, dispatches through adapters declared in `forwarders.enabled` per `tools/forwarder-relay/README.md`, applies the matched adapter's preamble-detect + credit-extract + reporter- addressing rules, and hands the routing decision back. Never mutates tracker state on its own.

  • Security issue import

    apache/magpie/skills/security-issue-import Skill

    145★ repo

    Scan <security-list> for reports that have not yet been copied into <tracker> as tracking issues, present the proposed imports to the user, and — defaulting to *import unless the user rejects upfront* — create the tracking issues with the `Needs triage` project-board status and draft a receipt-of- confirmation reply to each reporter. This is the first step of the handling process: the entry point that converts an inbound email thread into a tracker the rest of the skills (security-issue-sync, security-issue-fix, generate-cve-json) operate on.

  • Security issue invalidate

    apache/magpie/skills/security-issue-invalidate Skill

    145★ repo

    Close an `<tracker>` tracking issue as invalid: apply the `invalid` label, remove the scope label, post a short closing comment, archive the item from the project board, and — for trackers imported from `<security-list>` — draft a polite-but-firm reply to the reporter on the original Gmail thread explaining the team's reasoning (extracted from the tracker's discussion). For trackers opened via `security-issue-import-from-pr`, the email-draft step is skipped per the *no outreach to the PR author* rule of that skill.

  • Security issue sync

    apache/magpie/skills/security-issue-sync Skill

    145★ repo

    Synchronize a security issue in <tracker> with the state of its GitHub discussion, the <security-list> mailing thread, and any <upstream> PRs that fix it. The skill gathers all relevant signals and proposes label / milestone / assignee / field / draft-email updates — applying only what the user has explicitly confirmed. Suggests the next step in the handling process and prints the CVE allocation link when a CVE is needed.

  • Security issue triage

    apache/magpie/skills/security-issue-triage Skill

    145★ repo

    For each open `<tracker>` issue carrying the `needs triage` label, read body + comments and classify the candidate disposition into one of six classes: VALID / DEFENSE-IN-DEPTH / INFO-ONLY / INVALID / PROBABLE-DUP / FIX-ALREADY-PUBLIC. On user confirmation, posts a triage-proposal comment that invites the security team to react. Read-only on tracker state — no label flips, closes, or CVE allocations. Supports `--retriage` for re-litigating passed-triage decisions when substantive new activity lands.

  • Security tracker stats dashboard

    apache/magpie/skills/security-tracker-stats-dashboard Skill

    145★ repo

    Generate a self-contained HTML dashboard of `<tracker>` repository statistics for security-team review.

  • Setup isolated setup doctor

    apache/magpie/skills/setup-isolated-setup-doctor Skill

    145★ repo

    Probe the secure-agent setup for in-session functional restrictions that block legitimate workflows. Three live probes — SSH agent / Yubikey reachability, localhost port binding, docker / podman runtime socket — each pointing the user at the matching numbered troubleshooting entry and its settings.json remediation (see body). Read-only — never modifies settings.json, never invokes the sandbox bypass.

  • Setup isolated setup install

    apache/magpie/skills/setup-isolated-setup-install Skill

    145★ repo

    Guide an adopter through the first-time install of the framework's secure agent setup (bubblewrap + socat + claude-code, sandbox/permissions/clean-env layers). Walks every step interactively; never auto-runs sudo, shell-rc edits, or settings overwrites.

  • Setup isolated setup update

    apache/magpie/skills/setup-isolated-setup-update Skill

    145★ repo

    Surface drift between the user's installed secure agent setup and the framework's latest (framework checkout, pinned tools, user-scope script copies, denial commands, comdev MCP checkouts). Read-only — surfaces candidates and diffs, never auto-applies. The user decides what to update.

  • Setup isolated setup verify

    apache/magpie/skills/setup-isolated-setup-verify Skill

    145★ repo

    Walk the verification checklist for the framework's secure agent setup and report ✓ done / ✗ missing / ⚠ partial for each check, with concrete evidence (file paths, command output, version strings). Covers nine checks across settings wiring, installed tool versions, and sandbox configuration. Read-only — never modifies anything.

  • Setup override upstream

    apache/magpie/skills/setup-override-upstream Skill

    145★ repo

    Walk an adopter through promoting a local `.apache-magpie-overrides/<skill>.md` file into a PR against `apache/magpie`. After the PR merges and the adopter runs `/magpie-setup upgrade`, the override file is no longer needed and the skill prompts for its removal.

  • Setup shared config sync

    apache/magpie/skills/setup-shared-config-sync Skill

    145★ repo

    Commit + push the user's shared Claude config to the `~/.claude-config` private dotfile-style sync repo. Inspects for uncommitted local edits and unpushed commits, drafts a commit message, and after explicit approval commits and pushes. Runs `git pull --rebase` first if the local checkout is behind, so a push never overwrites concurrent work from another machine. Bootstraps the repo when it is missing: clones the default private remote if it exists, or creates a new private remote + scaffolds the minimal layout if it does not. Never force-pushes; never rewrites already-pushed history; never creates a public remote; never modifies files outside `~/.claude-config/` (except the confirmed fresh-host symlink wiring into `~/.claude/`).

  • Setup status

    apache/magpie/skills/setup-status Skill

    145★ repo

    Show how the apache-magpie framework is adopted in the current repo, then adjust that setup in place. Renders a Markdown adoption dashboard: install method and pin, drift, the wired agent targets, the installed skill families, and symlink health. From the same view the user can add or drop agent targets and skill families; the actual change runs through the setup skill.

  • Setup upstream fix

    apache/magpie/skills/setup-upstream-fix Skill

    145★ repo

    Turn a framework bug or quirk the agent hit while running a Magpie skill or tool into a fix PR against `apache/magpie` — one PR per issue. First confirms the problem is a framework defect (not a local misconfiguration or a stale snapshot), then searches `apache/magpie` for an existing issue or PR that already covers it, and only proposes a new fix PR when none exists — otherwise it points the user at the pending one.

  • Setup

    apache/magpie/skills/setup Skill

    145★ repo

    Adopt and maintain the apache-magpie framework in a project repo via the snapshot-based adoption mechanism. The only framework skill committed in an adopter's repo; every other skill is a symlink the adopt sub-action wires up. Sub-actions: `/magpie-setup` - first-time adoption (default; main-checkout only) `/magpie-setup upgrade` - refresh the gitignored snapshot per the committed lock (main-checkout only) `/magpie-setup worktree-init` - symlink a worktree's snapshot to the main's `/magpie-setup verify` - health check + drift detection `/magpie-setup skill-sources` - fetch/pin/symlink skills from trusted external sources listed in the adopter trust list (main-checkout only) `/magpie-setup override <skill>` - open or scaffold an agentic override in `.apache-magpie-overrides/` `/magpie-setup unadopt` - reverse the adoption (snapshot, locks, symlinks, hook, doc sections); preserves `.apache-magpie-overrides/` by default (main-checkout only)

  • Workflow security audit

    apache/magpie/skills/workflow-security-audit Skill

    145★ repo

    Read-only GitHub Actions workflow security audit for one repository, an explicit repository set, or a whole GitHub org. Runs `zizmor` to surface injection vulnerabilities, excessive permissions, unpinned external actions, and self-hosted-runner fork-secret leaks. Produces a grouped, prioritised finding report; never edits workflow files, opens PRs, or posts comments.

  • Generate cve json

    apache/magpie/tools/cve-tool-vulnogram/generate-cve-json Skill

    145★ repo

    Generate a CVE 5.x JSON document from an <tracker> tracking issue, ready to paste into the Vulnogram `#source` tab of the ASF CVE tool at https://cveprocess.apache.org/cve5/<CVE-ID>#source. The conversion is deterministic: same issue in, same JSON bytes out. Handles multiple credits (one per line) and multiple references (URLs extracted from the issue's "Public advisory URL" and "PR with the fix" fields; the "Security mailing list thread" field is treated as internal-only and never exported).

  • Enrich with aws security agent

    aws-samples/sample-devops-agent-tools/skills/enrich-with-aws-security-agent Skill

    143★ repo

    Automatically load this skill when investigating application outages, service degradation, or errors that could have security-related root causes — including unexplained downtime, authentication or authorization failures, injection attacks, data exposure, or suspicious application behavior. Query AWS Security Agent CloudWatch logs to retrieve detailed code review findings with actionable, low-level details (file, line number, vulnerability type) that customers can directly fix.

  • Rds operation review

    aws-samples/sample-devops-agent-tools/skills/rds-operation-review Skill

    143★ repo

    Comprehensive Amazon RDS and Aurora operational review aligned with the AWS Well-Architected Framework and RDS/Aurora best practices. Use this skill when a user asks to review, audit, or assess RDS instances or Aurora clusters for best practices compliance, security posture, reliability, performance, cost optimization, backups, encryption, or operational readiness. Triggers on requests like "RDS review", "Aurora best practices audit", "database operational assessment", "review my RDS instance", "RDS health check", or "ORR for RDS".

  • Wiz security context

    aws-samples/sample-devops-agent-tools/skills/wiz-security-context Skill

    143★ repo

    Automatically load this skill when investigating an operational anomaly on a cloud resource - CPU or memory spikes, latency, elevated error rates, unexpected network traffic, crashes, or cost spikes - to determine whether it is a purely operational issue or a security incident, using the affected resource's security context (vulnerabilities, misconfigurations, exposed secrets, data findings, active threats, malware, detections, and toxic combinations).

  • Best practices

    vinta/hal-9000/skills/hal-skills/best-practices Skill

    143★ repo

    Use when the user asks about best practices, gotchas, common pitfalls, or recommended patterns for tools, libraries, config formats, API patterns, or project setup, or when setting up, configuring, choosing, or refining these where outdated guidance causes debugging pain. Also use when the user says "search online", "how should I", or "what's the best way to"

  • Refactor agents md

    vinta/hal-9000/skills/hal-skills/refactor-agents-md Skill

    143★ repo

    Use when refactoring a user-level or project-level AGENTS.md for progressive disclosure

  • Refactor claude md

    vinta/hal-9000/skills/hal-skills/refactor-claude-md Skill

    143★ repo

    Use when refactoring a user-level or project-level CLAUDE.md for progressive disclosure

  • Docker

    Dave-London/Pare/io.github.Dave-London/docker MCP server

    141★ repo

    Structured Docker operations (ps, images, logs, build) as typed JSON.

  • Http

    Dave-London/Pare/io.github.Dave-London/http MCP server

    141★ repo

    MCP server for HTTP requests (curl) with structured, token-efficient output

  • Pare docker

    Dave-London/Pare/io.github.Dave-London/pare-docker MCP server

    141★ repo

    Pare Docker ג€” Structured Docker operations (ps, images, logs, build, compose) as typed JSON.

  • Make

    Dave-London/Pare/io.github.Dave-London/make MCP server

    141★ repo

    MCP server for Make/Just task runners with structured, token-efficient output

  • Github

    Dave-London/Pare/io.github.Dave-London/github MCP server

    141★ repo

    MCP server for GitHub operations (PRs, issues, actions) with structured, token-efficient output

  • Pare test

    Dave-London/Pare/io.github.Dave-London/pare-test MCP server

    141★ repo

    Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON.

  • Search

    Dave-London/Pare/io.github.Dave-London/search MCP server

    141★ repo

    MCP server for code search (ripgrep + fd) with structured, token-efficient output