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 PromptPartner/agentsmith --skill grill-with-docsgit clone --depth 1 https://github.com/PromptPartner/agentsmithWrote 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/promptpartner/agentsmith/grill-with-docs)<a href="https://agentmods.dev/skills/promptpartner/agentsmith/grill-with-docs"><img src="https://agentmods.dev/badge/skills/promptpartner/agentsmith/grill-with-docs/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/promptpartner/agentsmith/grill-with-docs"><img src="https://agentmods.dev/badge/skills/promptpartner/agentsmith/grill-with-docs.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.00055 | $0.00805 |
| Opus 5.5 | $0.00022 | $0.00322 |
| Sonnet 5.5 | $0.00011 | $0.00161 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
grill-with-docs 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 26d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill with docs
Resolve a change's design tree with the operator while recording each answer where a fresh session can use it. Stop at a handoff-ready plan; implementation is a separate unit of work.
Route
- Use this workflow when a repository change is fuzzy but can be settled in one session.
- Use
wayfinderwhen the destination spans sessions, has dependent decisions that need separate research, or cannot yet become one implementation plan. - Use the ordinary plan flow when scope, language, and consequential choices are already settled.
Establish the tree
- Read the tracked item, existing plan/spec,
CONTEXT-MAP.md, relevantCONTEXT.mdfiles, ADRs, and the code or assets that constrain the change. Facts come from the repository; decisions come from the operator. - Locate the project's plan convention. Reuse an existing change plan; otherwise create one from
.harness/templates/plan.md,templates/plan.md, or the same shape at.planning/<slug>.md, in that order of availability. - Map the unresolved choices as a design tree. Its frontier is the independent questions whose prerequisites are settled now.
Work the frontier
Ask a small numbered round from the frontier. For each question, state why it matters, the real options and trade-offs, and your recommended answer. Then wait for the operator's decisions.
After each answer round:
- Recompute the tree. Cross-check claims against the repository and surface contradictions.
- Record every settled decision in the plan with its original precision: boundaries, ordering, defaults, failure behaviour, numeric constraints, and evidence requirements.
- Record resolved project language and qualifying ADRs before the next question round.
Repeat until the frontier is empty. A question that depends on an unresolved answer stays off the current frontier.
Durable artifacts
Plan
The plan is the complete decision ledger and implementation handoff. Keep its scope, approach, risks, verification, and done criteria current after each round. Place rationale once: in the plan for ordinary choices, or in an ADR for a qualifying architectural choice with a link from the plan.
What ships with it
2 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.
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.
- 26d ago First seen · 75 lines · 55 tokens per session scan A e7dccd69bfe7
grill-with-docs is a skill published in the GitHub repository PromptPartner/agentsmith (178 stars, last pushed 4d ago), licensed MIT. It adds 55 tokens to every session and 805 once invoked, about $0.0002 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-09-20.
Other skills, from other repositories
web-animation-css-animations
CSS animation patterns - transitions, keyframes, scroll-driven timelines, @property, compositor-friendly properties, prefers-reduced-motion.
meta-config-stack-detect
Inspect a codebase, a stack the user describes, or a description of what they want to build; map what is there to agents-inc catalog skills — or intent to candidate built-in stacks the user picks from — and emit a SeedPayload plus a human-readable proposal report. Use when seeding a configuration for a project that…
meta-design-composable-components
Composable component APIs — parts, state, polymorphism.
ai-provider-anthropic-sdk
Official Anthropic SDK patterns for TypeScript/Node.js — client setup, Messages API, streaming, tool use, vision, extended thinking, structured outputs, prompt caching, batch API, and production best practices.
api-baas-appwrite
Appwrite backend-as-a-service — Auth, TablesDB, Storage, Functions, Realtime, permissions model, typed client.
api-baas-firebase
Firebase backend-as-a-service — Firestore, Authentication, Cloud Functions v2, Storage, Hosting, Admin SDK, security rules, emulator suite.