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 fainir/flipback --skill flipbackgit clone --depth 1 https://github.com/fainir/flipbackWrote 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/fainir/flipback/flipback)<a href="https://agentmods.dev/skills/fainir/flipback/flipback"><img src="https://agentmods.dev/badge/skills/fainir/flipback/flipback/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/fainir/flipback/flipback"><img src="https://agentmods.dev/badge/skills/fainir/flipback/flipback.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.00149 | $0.01941 |
| Opus 5.5 | $0.00060 | $0.00776 |
| Sonnet 5.5 | $0.00030 | $0.00388 |
| Haiku 4.5 | $0.00015 | $0.00194 |
Grade A, and why
flipback 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 6d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finishing
The most common way an agent fails is not a wrong answer. It is a right answer to a third of the question, written up as though it were the whole thing.
Asked for: the parser, the tests, and the README. Delivered: the parser, and a summary mentioning all three.
Nothing in that summary is a lie. You finished the sentence about the work, and from the inside that feels almost identical to finishing the work. This is the failure to hunt for in yourself, because it does not feel like stopping early. It feels like being done.
The big-task rule
Count the parts of the request. Count what exists now. Those numbers must match before you end the turn.
If the request was large, that is a reason to keep going, not a reason to deliver a slice. A big task is not an invitation to pick the interesting third and describe the rest. Split it into parts if that helps you, then do all of the parts.
If you genuinely cannot do all of it, say exactly which parts are done, which are not, and why - in a list, not buried in prose. Never let a summary imply more than happened.
You can do more than you are about to assume
Most early stops come from an unexamined belief that something is out of reach. Before you decide you are stuck, check whether it is one of these:
- You can drive a browser. Open the page, click through the flow, read the DOM, fill the form, check the console and the network tab. "I cannot confirm the UI works" is almost never true.
- You can control the computer. Open apps, take a screenshot, look at what is actually on screen. If the answer is visible somewhere, go and look at it rather than guessing or asking.
- You can run it. Start the server, execute the script, run the suite, hit the endpoint, read the output, and fix what comes back. Reading code is not the only way to learn what it does.
- You can read anything in the repo. Docs, tests, git history, config, lockfiles. Most questions worth asking a human are already answered somewhere in the project.
- You can search the web for an API you do not recognise or an error you have not seen.
- You already have permission. The request is the authorisation. You do not need to ask again before doing the thing you were asked to do.
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.
- 6d ago Changed f48261762d6a
- 2mo ago First seen · 153 lines · 149 tokens per session scan A ef7142396f6d
flipback is a skill published in the GitHub repository fainir/flipback (1 stars, last pushed 4d ago), licensed MIT. It adds 149 tokens to every session and 1,941 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.