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 jsuvic/agent-profile --skill grill-changegit clone --depth 1 https://github.com/jsuvic/agent-profileWrote 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/jsuvic/agent-profile/grill-change)<a href="https://agentmods.dev/skills/jsuvic/agent-profile/grill-change"><img src="https://agentmods.dev/badge/skills/jsuvic/agent-profile/grill-change.svg" alt="Measured on agentmods" 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.00031 | $0.00818 |
| Opus 5 | $0.00015 | $0.00409 |
| Sonnet 5 | $0.00006 | $0.00164 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
grill-change 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 7d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grill Change
Purpose
Clarify a stakeholder request before any spec, issue plan, or implementation work starts. The output is an agreement record for a follow-up synthesis workflow; it is not an implementation plan.
Operating Rules
- Ask one focused question, then wait for the user's answer.
- Include a recommended answer with the question and explain why that answer is safest for the project.
- Inspect relevant local specs, ADRs, docs, fixtures, and code before asking questions that local context can answer.
- Challenge vague terms, overloaded words, and claims that conflict with repository evidence.
- Prefer concrete examples, edge cases, and tradeoff choices over broad brainstorming.
- Keep implementation details provisional until the product intent and non-goals are settled.
- Capture durable terms and hard-to-reverse decisions in the agreement record when they crystallize.
- Do not create issue lists, edit files, or start implementation during the grill.
Question Format
Use this shape for each question:
Question: <one decision or missing fact>
Recommended answer: <the default direction you would choose>
Why: <short reason based on product intent, safety, contracts, or repo evidence>
Design-it-Twice
For a hard-to-reverse choice, present it as a Design-it-Twice question: sketch two genuinely different paths before recommending one.
Path A: <approach> - interface: <the shape callers see>; risks: <what could go wrong>.
Path B: <a genuinely different approach> - interface: <the shape callers see>; risks: <what could go wrong>.
Recommendation: <the path you would choose and why>.
Do not offer two variations of the same path. Reserve this form for choices that are expensive to change later; a routine choice needs one recommended answer, not two paths.
ADR Candidates
Capture a decision as an ADR candidate when it is hard to reverse, surprising without context, or carries real trade-offs. Record the decision, the alternatives considered, and the reason as an agreement-record note only. Do not write an ADR file during the grill; synthesis persists it after approval.
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.
- 7d ago First seen · 87 lines · 31 tokens per session scan A 1dec73131d8e
grill-change is a skill published in the GitHub repository jsuvic/agent-profile (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 31 tokens to every session and 818 once invoked, about $0.0002 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-31.
Other skills, from other repositories
hasdata
Use HasData to scrape any public web page, run real-time Google/Bing/Google-AI-Mode search queries, pull structured data from e-commerce, real-estate, lodging, jobs, maps, travel, video, and social platforms, or run async bulk-scraping and crawling jobs without managing proxies, browsers, or captchas. Reach for this…
hasdata-cli
Fetch real-time web data via the hasdata CLI. Use when the user wants search results, news, fact-checks, product or seller info, current prices, reviews, real-estate listings or sold comps, hotel rates or vacation rentals, local-business contact details, business owner posts/offers, job postings, salary research…
tastemaker
Generate genuinely beautiful, on-brand UI instead of generic "AI slop" — use whenever the user asks to build, design, style, or improve a UI, landing page, dashboard, app screen, or component, whenever a PRD/spec needs a design pass before implementation, whenever the user pastes reference images/Pinterest/Dribbble…
fde
Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a…
kubernetes-skill
Prevent Kubernetes hallucinations by diagnosing and fixing failure modes: insecure workload defaults, resource starvation, network exposure, privilege sprawl, fragile rollouts, and API drift. Use when generating, reviewing, refactoring, or migrating manifests, Helm charts, Kustomize overlays, cluster policies, and…
image-to-psd
A skill that reconstructs images as editable, layered Photoshop files. It separates the repaired background, visual components, and text into layers instead of leaving the page as one flat image.