Borrowing it
Nothing to install: this file belongs to proggarapsody/bitbottle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/proggarapsody/bitbottle/main/.agents/skills/ask-matt/SKILL.mdgit clone --depth 1 https://github.com/proggarapsody/bitbottleWrote 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/proggarapsody/bitbottle/ask-matt)<a href="https://agentmods.dev/skills/proggarapsody/bitbottle/ask-matt"><img src="https://agentmods.dev/badge/skills/proggarapsody/bitbottle/ask-matt/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/proggarapsody/bitbottle/ask-matt"><img src="https://agentmods.dev/badge/skills/proggarapsody/bitbottle/ask-matt.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.00022 | $0.02961 |
| Opus 5.5 | $0.00009 | $0.01184 |
| Sonnet 5.5 | $0.00004 | $0.00592 |
| Haiku 4.5 | $0.00002 | $0.00296 |
Grade A, and why
ask-matt 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 18d 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.
This is a copy
89% identical to ask-matt — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask Matt
You don't remember every skill, so ask.
A flow is a path through the skills. Most paths run along one main flow, and two on-ramps merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.
The main flow: idea → ship
The route most work travels. You have an idea and want it built.
/grill-with-docssharpens the idea by interview. Start here whenever you are working in a working directory: it's stateful, retaining what it learns inGLOSSARY.mdand ADRs. (No working directory? Use/grill-meinstead, covered under Standalone. Both run the same/grillingprimitive;grill-with-docsis the one that leaves a paper trail, which makes it the better of the two whenever a repo is there to leave it in.)- Branch: can you settle every question in conversation? If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by
/handoffin both directions (a prototype lives in its own directory, which is exactly what/handoffis for; see Phase boundaries):/handoffout, then open a fresh session against that file,/prototypeto answer the question with throwaway code,/handoffback what you learned, and reference it from the original idea thread.
- Branch: is this a multi-session build?
- Yes →
/to-spec(turn the thread into a spec), then/to-ticketsto split it into tracer-bullet tickets, each declaring its blocking edges. Then work the tickets one of two ways:/implementper ticket,/clearing context between each one. On a local tracker that's one file per ticket under.scratch/<feature>/issues/, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed. Each ticket is self-contained, so the last one's context is disposable./implement-specfor the whole spec in one run. It reads the tickets as a task graph, runs implementer subagents across the ready frontier in parallel, and lands everything on one integration branch. Reach for it when you'd rather orchestrate the build than drive each ticket yourself.
- No →
/implementright here, in the same context window.
- Yes →
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.
- 18d ago First seen · 96 lines · 22 tokens per session scan A 32b3c71d6dbb
ask-matt is a skill published in the GitHub repository proggarapsody/bitbottle (3 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 2,961 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to ask-matt, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
agent-inspect
Local evidence debugger and trajectory-test toolkit for TypeScript AI agents. Use when capturing framework-faithful traces, asserting TraceContract/TraceFacts, packaging Evidence v2, or inspecting local runs over read-only MCP (gettracefacts).
greenlight
It now lives at skills/greenlight/SKILL.md.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
mcp-bash
Build, debug and package MCP servers written in Bash with the mcp-bash framework (mcp-bash-framework). Use whenever the user wants to create an MCP server from shell scripts or CLIs, add or fix tools, resources, prompts or completions in an mcp-bash project, wire one into Claude Desktop, Cursor or another client…
deploy-setup
Wire up a freshly scaffolded Starter Series project for its first release — detect the template, register required GitHub secrets, set up OIDC trusted publishing where applicable, and trigger the first CD run. Pairs with the create skill (you scaffold first, then run this).