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 arunveersingh/ai --skill day-06-quote-the-payloadgit clone --depth 1 https://github.com/arunveersingh/aiWrote 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/arunveersingh/ai/day-06-quote-the-payload)<a href="https://agentmods.dev/skills/arunveersingh/ai/day-06-quote-the-payload"><img src="https://agentmods.dev/badge/skills/arunveersingh/ai/day-06-quote-the-payload/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/arunveersingh/ai/day-06-quote-the-payload"><img src="https://agentmods.dev/badge/skills/arunveersingh/ai/day-06-quote-the-payload.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.00093 | $0.00786 |
| Opus 5.5 | $0.00037 | $0.00314 |
| Sonnet 5.5 | $0.00019 | $0.00157 |
| Haiku 4.5 | $0.00009 | $0.00079 |
Grade A, and why
quote-the-payload 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quote the payload
Your agent runs the tests and says "no failures, safe to merge." The tool actually printed no tests ran, exit code 4: the path was wrong, so nothing was checked.
A summary of a tool result is not the result. The fix has two parts. Ask: the raw output comes before any interpretation, error or empty means stop, and the reply ends with one fixed verdict. Verify: check the quotes against the real output, and let a script's exit code decide "passed."
Paste Part A into the agent's standing instructions or before the task. Do Part B yourself. Fill in the brackets.
Part A — Ask (paste and adapt)
When you use a tool (run a command, call an API, search):
1. After each call, before saying what it means, show:
COMMAND: the exact command or call
EXIT: the exit code or status (write "not shown" if you don't
have it)
OUTPUT: the last 20 lines, word for word, in a code block
2. Success means: [YOUR CHECK, e.g. exit code 0 AND at least one
test passed]. Anything else is not success.
3. If the output is an error, is empty, or says nothing ran, write
STOPPED: <one line why>. Do not guess the result. Do not move to
the next step. You may propose one fix.
4. Only report results for calls you actually made in this session.
If you didn't run it, say NOT RUN.
5. End with one verdict: PASSED, FAILED, STOPPED, or NOT RUN.
Adapting it: for searches and API calls, set success to "at least one result" or "status 200 with a non-empty body." Ask for the write-up (merge note, summary, email) in a later message, after the verdict.
Part B — Verify (you do this)
- Check every quote is real. Real output (expand the tool call) in
raw.log, quoted lines inquoted.txt(one per line):! grep -vxFf raw.log quoted.txtIt prints any quoted line the tool never printed and fails if there is one. - Gate the run with a script. Have the agent run
check_tests.shfrom the lesson instead of barepytest. Pass =GATE PASSEDonly when pytest exits 0 and at least one test passed. Wrong path, all skipped, or a failing test printGATE FAILED. - Let CI decide the merge. Run the same script in CI and require it before merging. Add
set -o pipefailif your script pipes anything. - Stop on empty in code. If you build the agent, end the step with a fixed message when a tool errors or returns nothing, instead of passing
[]to the model to describe.
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 · 47 lines · 93 tokens per session scan A e29cd42cc4eb
quote-the-payload is a skill published in the GitHub repository arunveersingh/ai (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 93 tokens to every session and 786 once invoked, about $0.0004 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-10-08.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…