Borrowing it
Nothing to install: this file belongs to design-and-deliver/claude-code-autoconfig. 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/design-and-deliver/claude-code-autoconfig/main/.claude/commands/gimme-one-liner.mdgit clone --depth 1 https://github.com/design-and-deliver/claude-code-autoconfigWrote 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/commands/design-and-deliver/claude-code-autoconfig/gimme-one-liner)<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/gimme-one-liner"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/gimme-one-liner/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/commands/design-and-deliver/claude-code-autoconfig/gimme-one-liner"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/gimme-one-liner.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.00000 | $0.00685 |
| Opus 5 | $0.00000 | $0.00342 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
gimme-one-liner 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gimme One-Liner
Collapse whatever was just investigated in this conversation into exactly three lines.
This command exists because a finished investigation is usually reported at the length it took to conduct — the false starts, the tools that disagreed, the evidence trail. That narration is worth having while the work is live and worthless once it lands. This is the landing form.
Scope
The subject is the most recent investigation, debugging thread, or diagnosis in this conversation — not the whole session, and not the last thing you happened to say. If the conversation moved on to unrelated work after the investigation closed, the investigation is still the subject.
You already know the answer. Do not re-run tools, re-read files, or re-verify to write this — it is a compression of context you hold, not a fresh pass. The one exception: if you are about to state something as fact that you never actually confirmed, check it or drop it.
Output — exactly three lines
**Root cause:** <the mechanism, in one sentence>
**Conclusion:** <where it stands now, in one sentence>
**Fix:** <what remains to be done, in one sentence — or "None." >
Nothing before the first line, nothing after the last. No preamble, no heading, no recap, no closing offer, no bullets, no table.
Rules per line:
- Root cause names the mechanism, not the symptom. "The log wrote
(complete)before the result was known" is a mechanism; "beeps were silent" is a symptom. If the root cause was never actually established, say so plainly —Root cause: not established; <what is known>— rather than promoting the leading theory to a finding. - Conclusion is the current state: fixed, fixed-and-tested, open, or won't-fix. Name the commit hash if there is one. This is where an outcome that contradicts an earlier claim in the conversation gets stated, briefly and without re-litigating it.
- Fix is what is still outstanding. If the work is done, this is
None.— do not restate the fix that already landed, which belongs to Conclusion. Anything discovered along the way but deliberately not done goes here in a clause, not a paragraph.
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 · 58 lines · 0 tokens per session scan A 1a4762eb32f6
gimme-one-liner is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 685 tokens. 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.