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 nicepkg/ai-workflow --skill legacy-to-ai-readygit clone --depth 1 https://github.com/nicepkg/ai-workflowWrote 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/nicepkg/ai-workflow/legacy-to-ai-ready)<a href="https://agentmods.dev/skills/nicepkg/ai-workflow/legacy-to-ai-ready"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/legacy-to-ai-ready/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/nicepkg/ai-workflow/legacy-to-ai-ready"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/legacy-to-ai-ready.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.00107 | $0.02190 |
| Opus 5 | $0.00053 | $0.01095 |
| Sonnet 5 | $0.00021 | $0.00438 |
| Haiku 4.5 | $0.00011 | $0.00219 |
Grade A, and why
legacy-to-ai-ready 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legacy to AI-Ready
Transform legacy codebases into AI-ready projects by generating Claude Code configurations.
Quick Start (5-Minute Setup)
For most projects, start with just CLAUDE.md:
- Analyze:
python scripts/analyze_codebase.py [path] - Create CLAUDE.md with build commands, code style, architecture overview
- Done - Claude can now write code following your project's conventions
Expand to full configuration only when needed.
Interactive Discovery
Before generating configs, ask these questions:
Project Scope:
- What is this project? (web app, API, CLI, library)
- Primary language and frameworks?
- Team size? (solo, small team, enterprise)
Pain Points:
- What mistakes do new developers commonly make?
- What patterns should always be followed?
- What operations are repeated frequently?
Integration Needs:
- External services used? (databases, APIs, cloud)
- CI/CD pipeline? (GitHub Actions, Jenkins)
- Code quality tools? (linters, formatters)
Configuration Decision Tree
Start
│
├─ Small project / Solo dev
│ └─ CLAUDE.md only
│
├─ Team project
│ ├─ Multi-language? → Add .claude/rules/
│ ├─ Complex domain? → Add .claude/skills/
│ ├─ Code reviews? → Add .claude/agents/
│ └─ Repeated tasks? → Add .claude/commands/
│
└─ Enterprise / Large team
└─ All configurations + MCP servers + Hooks
Generated Configurations
| Config | Purpose | When to Create |
|---|---|---|
| CLAUDE.md | Project memory (shared) | Always (required) |
| CLAUDE.local.md | Personal preferences (git-ignored) | Individual customization |
| .claudeignore | Files Claude should not access | Sensitive files exist |
| .claude/rules/ | Path-specific rules | Multi-module projects |
| .claude/skills/ | Domain knowledge | Complex business logic |
| .claude/agents/ | Task specialists | Repeated review/debug tasks |
| .claude/commands/ | Quick prompts | Common workflows |
| .claude/settings.json | Hooks + permissions | Auto-formatting, security |
| MCP servers | External tools | Database/API integrations |
What ships with it
26 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/CLAUDE.md.template 1.1 KB
- assets/claudeignore.template 812 B
- assets/resource-scout/references/sources.md 7.6 KB
- assets/resource-scout/SKILL.md 4.8 KB
- assets/settings.json.template 430 B
- assets/skill-creator/references/output-patterns.md 1.8 KB
- assets/skill-creator/references/workflows.md 819 B
- assets/skill-creator/scripts/init_skill.py 11 KB runs code
- assets/skill-creator/scripts/package_skill.py 3.2 KB runs code
- assets/skill-creator/scripts/quick_validate.py 3.4 KB runs code
- assets/skill-creator/SKILL.md 17 KB
- assets/skill-downloader/scripts/download_from_archive.py 7.5 KB runs code
- assets/skill-downloader/scripts/download_from_github.py 6.9 KB runs code
- assets/skill-downloader/scripts/download_skill.py 5.4 KB runs code
- assets/skill-downloader/SKILL.md 4.1 KB
- references/advanced-patterns.md 8.7 KB
- references/agents-patterns.md 5.8 KB
- references/claude-md-patterns.md 3.7 KB
- references/commands-patterns.md 6.0 KB
- references/examples.md 9.4 KB
- references/hooks-patterns.md 6.5 KB
- references/mcp-patterns.md 3.9 KB
- references/resource-discovery.md 4.8 KB
- references/rules-patterns.md 5.5 KB
- references/skills-patterns.md 4.9 KB
- scripts/analyze_codebase.py 30 KB runs code
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.
- 10d ago First seen · 291 lines · 107 tokens per session scan A 133ae1593ac9
legacy-to-ai-ready is a skill published in the GitHub repository nicepkg/ai-workflow (283 stars, last pushed 7mo ago), licensed MIT. It adds 107 tokens to every session and 2,190 once invoked, about $0.0005 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-30.
Other skills, from other repositories
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
hive.pdf
Read, write, merge, split, rotate, watermark, encrypt, and OCR PDF files using Python (pypdf, pdfplumber, reportlab, pypdfium2) and command-line tools (poppler-utils, qpdf). Use when the user asks to extract text/tables/images from a PDF, create or modify a PDF, combine or split PDFs, OCR a scanned PDF…
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.