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 Kerliula/ship-me --skill solve-megit clone --depth 1 https://github.com/Kerliula/ship-meWrote 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/kerliula/ship-me/solve-me)<a href="https://agentmods.dev/skills/kerliula/ship-me/solve-me"><img src="https://agentmods.dev/badge/skills/kerliula/ship-me/solve-me/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/kerliula/ship-me/solve-me"><img src="https://agentmods.dev/badge/skills/kerliula/ship-me/solve-me.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.00139 | $0.03406 |
| Opus 5.5 | $0.00056 | $0.01362 |
| Sonnet 5.5 | $0.00028 | $0.00681 |
| Haiku 4.5 | $0.00014 | $0.00341 |
Grade A, and why
solve-me 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 1mo 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solve Me — Divide, Compare, Recommend
Your job is to design a solution on paper. No code. No framework names. Plain language only.
You are not allowed to say "use Laravel," "add a migration," "create an Eloquent model," "use Redis," or name any specific library, framework, or tool. Describe things at the level of: what data is stored, what steps happen, what checks are made, in what order, and why. Anyone reading it should be able to build it in any language or stack.
Write in plain, everyday language. Short sentences. Concrete words. If a smart non-technical person couldn't follow a paragraph, rewrite it simpler.
Input
You need a clear problem write-up before you can start. Accept it as:
- A path to a markdown file (e.g. the file
/grill-meproduced atdocs/grilling/<topic>.md), or - Problem details pasted directly into the conversation.
If neither is available, ask the developer for one. Don't invent the problem yourself — a fuzzy or assumed problem produces a fuzzy solution.
Read the problem write-up fully before doing anything else. Pull out: the rules, the limits, the edge cases, what must always stay true, and what's out of scope. These constrain every solution you propose — mention constraints, don't restate the whole doc.
Revising after a critique
If you're also given a critique file (docs/critique/<slug>.md, from
/critique-me), you're in a dialogue with the critic, not starting
over. This can happen several rounds in a row. Each round, read the
latest round of the critique, then:
- Answer every open Must fix finding, one of two ways:
- Fixed — change the solution.
- Disagree — say in one or two lines why the finding is wrong, with evidence (the grilling file, or why the standard approach doesn't fit here). Don't give in just to end the dialogue: a wrong fix is worse than an honest disagreement the developer settles. Never ignore one.
- Take a Worth considering finding only if it's clearly better; otherwise leave it for the developer.
- Keep the sub-problem numbers. Change only what a finding touches. A genuinely new sub-problem goes at the end with the next number.
- Re-run Step 3 (put it back together) on the result, and update
docs/breakers/<slug>.mdto match — add, fix or re-point cases. - Add this round to a section at the end, before Open trade-offs:
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.
- 1mo ago Changed · +77 lines · +26 tokens per session 8c356e6c7cf5
- 2mo ago First seen · 283 lines · 113 tokens per session scan A 2131daaa063d
solve-me is a skill published in the GitHub repository Kerliula/ship-me (1 stars, last pushed 1mo ago), licensed MIT. It adds 139 tokens to every session and 3,406 once invoked, about $0.0006 per session on Opus 5.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.
Other skills, from other repositories
laravel-upgrade
Upgrade a Laravel application across major versions safely (Laravel 8 -> 9 -> 10 -> 11 -> 12 -> 13), one hop at a time. Use when upgrading Laravel, when a composer update fails after a major bump, when deciding whether to hop versions by hand or pay for Laravel Shift, or when something compiled fine but broke at…
laravel-architecture-review
Review a Laravel codebase's architecture and design, not just its types. Use when asked to audit a Laravel app, find architectural smells, decide where business logic belongs (controller vs Action vs Service), whether a Repository/DDD/TDD layer is justified, or how to apply SOLID/DRY to a Laravel project. Runs the…
lahja
A writing guide for producing Arabic in a specific spoken dialect rather than formal Arabic or word-for-word translation. It focuses on grammar, spelling habits, common forms, and how technical English fits into the dialect.
filament-plugin-development
Build and publish custom Filament plugins (Filament is the Laravel admin-panel framework). Use when creating a Filament plugin/package, implementing the Plugin contract, scaffolding from the plugin skeleton, registering assets/resources/pages/render-hooks, making a configurable plugin, testing it, or publishing to…
geo-llm-optimization
Generative Engine Optimization (GEO) - make a website citable and recommended INSIDE AI-assistant answers (ChatGPT, Claude, Perplexity, Gemini), not just ranked on Google. Use when the user wants to be found now that people ask AI directly, wants to be a source LLMs pull from, or asks about llms.txt, AI crawler…
laravel-filament
Version-aware best practices for Filament (the Laravel admin-panel / TALL-stack framework by filamentphp), covering v1 through v5. Use whenever building, reviewing, or upgrading Filament resources, panels, forms/schemas, tables, actions, relation managers, widgets, or multi-tenancy. ALWAYS detects the installed…