Actionable Tools Index

Centralized registry of tools the agent can pick and use when Kevin says "I want to do X." Organized by intent, not by source. Each entry includes what it does, how to invoke it, and whether it's free/open-source.

How to Use This Page

When Kevin asks to accomplish a task, scan the intent categories below. If a tool matches, use it directly. Many tools are already installed as skills or CLI utilities - check the "invoke" column first.

This page is an operational registry, not a primary-source article. Entries originate from raw X bookmarks, dedicated wiki tool pages, installed skill files, and researched tool pages. The source trail should live on the dedicated page when a tool graduates; this index only keeps enough invocation detail to route work quickly. Source: raw/x-bookmarks/bookmarks.jsonl; skills/personal/; wiki/tools/

macOS app discovery

Use npm run harvest:mac-apps when a named workflow has a missing macOS capability. It produces a content-addressed Awesome-Mac snapshot with all 1,257 current candidates, 25 sections, 60 category paths, source lines, and catalog labels. Query that snapshot by the job; do not browse popularity and install a bundle. A shortlisted app still needs current official-source, license, maintenance, signing/notarization, OS/hardware, price, permissions, data, package-source, overlap, doctor, and uninstall checks. Catalog labels and the catalog's own conflicting CC0 / CC BY / CC-BY-SA metadata are not application authority. Source: X/@XAMTO_AI, 2026-07-16; jaywcjlove/awesome-mac@bab7c005; local harvest receipt, 2026-08-11

Guarded web-catalog discovery

Use npm run harvest:fmhy only after naming a legitimate capability gap. FMHY is retained because its catalog, curation process, safety/status notes, mirrors, and weekly bookmark/search projections carry strong discovery and architecture signals. The adapter deliberately emits a file manifest instead of thousands of links: 85 catalog pages, 101 supporting notes, exact Git blob hashes, and review lanes at fmhy/edit@72ea2b5. Candidate projection is off.

Open only the source slice relevant to the named job; verify the selected tool at its official source; check license, maintenance, security, price, data, overlap, and workflow fit; then add it to the normal owner/router. FMHY labels are source assertions. Do not use high-risk branches for unauthorized access, bulk-import its bookmarks, globally install SafeGuard, or republish the unlicensed catalog. Source: FMHY; local guarded-catalog harvest, 2026-08-11

Practical LLM curriculum discovery

Keep the complete pinned Dive into LLMs corpus as an 11-theme teaching and experiment-recipe source: fine-tuning/deployment, prompting/chain of thought, knowledge editing, math-reasoning distillation, text watermarking, jailbreaks, LLM steganography, multimodal models, GUI agents, agent safety, and RLHF. Select one chapter by a named learning or experiment goal, then run Research Experiment Workflow rather than installing the repository globally.

Current route boundary: source head f84c042 dates to 2025-10-10; seven of the 11 notebook files contain no code cells; only chapter 11 has a local requirements file; environments range from PyTorch 1.13.1/CUDA 11.6 to 2.6.0 and include mutable external clones, remote datasets/models, API keys, and up to eight visible GPUs; GitHub detects no license. Stars and free access make it a strong discovery signal, not current execution or redistribution authority. Trace current primary papers/repos, resolve rights, pin an isolated environment, pilot one case, and keep a replay receipt. Jailbreak/steganography/security lessons stay within explicit defensive scope. Source: X/@XAMTO_AI, 2026-07-21; Lordog/dive-into-llms@f84c042; local replay 2026-08-11

Open-source alternatives: capability-first routing

A saved ten-repository roundup is retained in full, but its subscription-price comparisons are discovery rhetoric rather than equivalence proof. Self-hosting still has hardware, maintenance, security, backup, upgrade, and operator costs; several products also have mixed or source-available licenses. Choose by the exact job and deployment boundary. Source: X/@Nozelcode, 2026-07-27; Source snapshots

The keep decision applies to all ten sources. “Keep” means searchable evidence and a deterministic route—not automatic installation, global endorsement, or a dedicated page per repository.

Coder apps: five different jobs

The saved roundup is useful, but “open-source and free apps” is not one verified category. Keep all five through the job they actually perform and preserve the license/deployment distinction. Source: X/@csaba_kissi, 2026-07-16; Source snapshots

The recovered video centers React Bits rather than demonstrating all five products. Its strongest harness signal is inspectability: a reusable visual source should expose preview, code, copyable prompt, live parameters, and reduced-motion behavior as separate reviewable states.

Retained July operator and utility candidates

The sources below remain searchable and routable because each carries a useful job or system signal. They are not rejected for being narrow, early, redundant, or not yet installed. A candidate becomes the default only after its exact job, rights, security/data boundary, maintenance, overlap, representative behavior, and rollback are proved. Source: commit-pinned repository evidence, captured 2026-08-12

Other July sources—including an early TikTok scraper, a free-provider coding gateway, Agentica examples, marketing skills, and individual visual utilities— remain in the evidence graph even when they do not justify a default. Media and marketing routes additionally require platform terms, source rights, consent, identity/factuality checks, and explicit approval before publish or spend.

---

Convert Documents to LLM-Ready Markdown

Transcribe Audio & Video

Download Media

Screen Recording & Sharing

Browse & Crawl the Web

Browser Automation & Testing

Design & UI - Fonts, Colors, Textures

Design Inspiration & Reference

SEO & AI Search Optimization (GEO)

Code Quality & Linting

AI Models & Model Routing

Security & Bug Detection

Self-Hosting & Deployment

Career & Job Search

Content Creation & Social Media

Agent Skills & Discovery

Agent Frameworks & Platforms

Documentation & Search

Animation & Creative Coding

Generative UI

Frontend Components & Libraries

Places to Launch & Get Users

---

AWS-shaped local emulation

Agent token & context cost

Design tool discovery

Native shell + web UI

Persisted browser playbooks

React hygiene

Cursor orchestration

shadcn-compatible registries

See Shadcn Registry Directory (Top Blocks) for the ranked vendor list (blocks, motion kits, layout packs).

---

Maintenance

This page is updated whenever new tools are discovered via X bookmarks, Obsidian clippings, or research automations. To add a tool: include the name, one-line purpose, invocation method, and whether it's free.

| Graphify | Builds a repo knowledge graph sidecar for topology/path/affected-node questions; qmd still owns wiki truth | npm run graphify:sidecar -- build . --no-viz; query via npm run graphify:sidecar -- query "..." | Yes, OSS |

---

Timeline

• 2026-08-11 | Added the callable macOS discovery action backed by the tested Awesome-Mac snapshot, while keeping current first-party verification, trial, doctor, and workflow binding between a catalog row and activation. Source: X/@XAMTO_AI; jaywcjlove/awesome-mac@bab7c005
• 2026-06-17 | Marked as a longform operational registry and clarified that durable source citations belong on dedicated tool pages. Source: raw/x-bookmarks/bookmarks.jsonl; wiki/tools/
• 2026-05-11 | Expanded the registry with agent, SEO/GEO, content, design, and frontend tooling discovered through wiki maintenance. Source: Wiki Log
• 2026-04-09 | Created the actionable tool registry from bookmark and skill sources. Source: raw/x-bookmarks/bookmarks.jsonl