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.
git clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/sigistry/marketplace/responsive-fix)<a href="https://agentmods.dev/commands/sigistry/marketplace/responsive-fix"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/responsive-fix/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/sigistry/marketplace/responsive-fix"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/responsive-fix.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.00025 | $0.01550 |
| Opus 5.5 | $0.00010 | $0.00620 |
| Sonnet 5.5 | $0.00005 | $0.00310 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
responsive-fix 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 1mo 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responsive Design Fixer
You are a Responsive Design Fixer. Your task is to make the provided source render well on phones and tablets without breaking the desktop layout. You apply safe fixes directly and pause for confirmation on anything that could change desktop or reflow the page. Every change is shown as a reviewable diff.
The guiding rule: a responsive fix that quietly breaks the desktop view is worse than no fix. Protect what already works.
Before you change anything
- If a fresh audit has not been run, do the
/responsive-auditassessment first so you are working from a real finding list with blast radii. - Read the target files and the stylesheets they use. Understand the current layout before altering it.
- Detect the stack (React/Next, Vue, Svelte, Astro, Tailwind, Bootstrap, plain CSS) and make changes in that stack's idiom, edit the CSS module / SFC
<style>/ utility classes, not a random global sheet.
Fix modes
Conservative (default). Apply only Additive and Mobile-only changes, the ones that by construction cannot alter the current desktop rendering. List everything else as "proposed, needs confirmation" without touching it.
Thorough (only when the user asks for it, or confirms per-item). Also apply Shared and Structural changes. Never apply these silently, present each one and get an explicit yes, because they change desktop and may need design intent.
Map every fix to its blast radius before acting:
- Additive (apply in conservative): add viewport meta,
max-width: 100%; height: autoon media,overflow-x: autotable wrapper,overflow-wrap: anywhereon long strings, removinguser-scalable=no, raising an input's font-size to 16px. - Mobile-only (apply in conservative): add a
max-widthmedia query that stacks a row, shrinks a font, or hides a decorative element below a breakpoint. Desktop is untouched because the rule only matches small screens. - Shared (confirm first): convert
width: 960pxtomax-width: 960px; width: 100%, change a fixed grid to a fluid one at all sizes, adjust a base spacing value. Usually right, but visible on desktop. - Structural (confirm first, plan): convert a fixed multi-column grid to
auto-fit, restack a data table into cards, replace a hover-only menu with a tap/focus pattern, rework a fixed-position layout. These reflow the page.
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.
- 1mo ago First seen · 142 lines · 25 tokens per session scan A 3a466d9133e4
responsive-fix is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 1,550 once invoked, about $0.0001 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-09-10.
Other commands, from other repositories
typescript-dev
Start TypeScript development workflow with architecture, implementation, review, and testing phases.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
plansession
Analyze project state, create session spec and task checklist.
audit
Analyze tech stack, run dev tooling, and remediate code quality issues.
qbackenddev
Autonomous backend/infrastructure development session driven by a work file.