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 aimeos/pagible --skill torquegit clone --depth 1 https://github.com/aimeos/pagibleWrote 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/aimeos/pagible/torque)<a href="https://agentmods.dev/skills/aimeos/pagible/torque"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/torque/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/aimeos/pagible/torque"><img src="https://agentmods.dev/badge/skills/aimeos/pagible/torque.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.00042 | $0.01159 |
| Opus 5.5 | $0.00017 | $0.00464 |
| Sonnet 5.5 | $0.00008 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
torque 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 5d 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.
Torque Theme Design System
Direction
Use a clean, robust and trustworthy layout that feels like a well-run workshop: concrete floor, graphite tools, signal red markings and clear fixed prices. Put booking, the phone number, the services with starting prices, the price list, current offers and the used cars first, followed by what builds trust: binding quotes, warranty-safe servicing, old parts returned, the rating, the team and the address. Show mechanics at work, cars on lifts, brakes, tyres, diagnostic testers, electric cars charging and clean vehicles for sale; avoid dirty or chaotic workshops, crashed cars, racing imagery, stock handshakes and manufacturer logos used as decoration.
Foundations
- Use only the markup and classes supplied by
./theme/views/. - Use system fonts (condensed uppercase display headings, sans-serif body, monospace for prices, durations, labels and specs) and the existing
--pico-*variables. - Keep page content within a
1280pxmaximum width. - Use the concrete (
#F3F4F2) background, graphite (#16191D,#2B3036) for text, heroes, team cards and the footer, signal red (#C8102E) for links, filled buttons, badges, prices and accents in headings, and amber (#F5A400) only for hazard stripes, the announcement dot and star ratings. - Use tight
0.25remcorners, thick top borders on cards, slanted buttons, badges and hero image frames, square avatars and hazard stripe bars before section headings; headings and buttons are uppercase.
Components
- Hero: a dark split hero with a single 4:3 workshop or vehicle photo in
files, shown in a slanted frame with a red block behind it, an eyebrow naming the garage type, city and founding year, a short headline with an accent in*...*and two actions ("Book service" and "Price list"). Nest service pages (servicing, brakes and tyres, diagnostics, electric and hybrid) and careers below a top-level page so the header keeps about six links next to the phone number and "Book service". - Figures and badges: cards in the
figureslayout for rating, founding year, number of lifts and warranty, shown as odometer read-outs, and in thebadgeslayout with white line icons for fixed-price quotes, warranty-safe servicing, old parts returned, courtesy cars and the breakdown service. - Services: cards in three columns with a photo, the service as title, a link to its page and a bold first line with the starting price followed by the duration as inline code.
- Used cars: a
pricingelement with one item per vehicle: a photo, the make and model as name, the price, the monthly rate in the text, features as inline code only (year, mileage, fuel, gearbox, power, one highlight) for the spec strip, "Book a test drive" as button and badges like "Certified" or "Price drop". - Price list:
pricingelements with one item per service group, features as list items with the duration as inline code and a bold price at the end, the most booked group highlighted, followed by a table and questions about quotes, parts and payment. - Offers: a
pricingelement with service coupons without images, each with the offer price, the regular price and code in the text and what is included as features. - Team: cards in four columns with 4:5 portraits, the name as title and a bold first line with the role and qualification.
- Tips:
blogpages below the tips page (status 2, hidden in navigation), each with an article, key figures, a vertical step timeline, questions and a call to action. - Contact: a hero with the workshop, a table with workshop, sales and breakdown hours, cards for the lounge, courtesy cars and key drop box, a map with directions and a contact form.
- Footer: service, customer and company links and a service reminder card; the layout adds the address, opening hours and notice from the garage config below it.
- Garage details: the
garageconfig adds the automotive business JSON-LD, the top bar with the announcement and breakdown number, the phone number and "Book service" button in the header, the footer address, hours and notice and the action bar for phones.
What ships with it
60 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.
- .gitattributes 60 B
- composer.json 806 B
- database/seeders/TorqueDemo.php 80 KB
- i18n/af.po 2.3 KB
- i18n/ar.po 2.7 KB
- i18n/az.po 2.5 KB
- i18n/bg.po 2.8 KB
- i18n/ca.po 2.4 KB
- i18n/cs.po 2.3 KB
- i18n/da.po 2.3 KB
- i18n/de.po 2.3 KB
- i18n/el.po 2.9 KB
- i18n/en.po 2.2 KB
- i18n/es.po 2.4 KB
- i18n/et.po 2.3 KB
- i18n/fa.po 2.8 KB
- i18n/fi.po 2.3 KB
- i18n/fr.po 2.4 KB
- i18n/he.po 2.5 KB
- i18n/hr.po 2.3 KB
- i18n/hu.po 2.4 KB
- i18n/id.po 2.3 KB
- i18n/it.po 2.4 KB
- i18n/ja.po 2.5 KB
- i18n/km.po 3.2 KB
- i18n/ko.po 2.4 KB
- i18n/lt.po 2.4 KB
- i18n/lv.po 2.4 KB
- i18n/messages.pot 1.7 KB
- i18n/nl.po 2.3 KB
- i18n/no.po 2.3 KB
- i18n/pl.po 2.3 KB
- i18n/pt-BR.po 2.4 KB
- i18n/pt.po 2.4 KB
- i18n/ro.po 2.4 KB
- i18n/ru.po 2.8 KB
- i18n/sk.po 2.3 KB
- i18n/sl.po 2.3 KB
- i18n/sr.po 2.8 KB
- i18n/sv.po 2.3 KB
- i18n/th.po 3.2 KB
- i18n/tr.po 2.3 KB
- i18n/uk.po 2.8 KB
- i18n/vi.po 2.5 KB
- i18n/zh-TW.po 2.3 KB
- i18n/zh.po 2.3 KB
- lang/af.json 221 B
- lang/ar.json 272 B
- lang/az.json 257 B
- lang/bg.json 295 B
- lang/ca.json 242 B
- lang/cs.json 242 B
- lang/da.json 222 B
- lang/de.json 245 B
- lang/el.json 322 B
- lang/en.json 227 B
- lang/es.json 234 B
- lang/et.json 232 B
- lang/fa.json 295 B
- lang/fi.json 232 B
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.
- 5d ago First seen · 47 lines · 42 tokens per session scan A 88891c21e075
torque is a skill published in the GitHub repository aimeos/pagible (596 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,159 once invoked, about $0.0002 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-13.
Other skills, from other repositories
api-designer
Designs production-grade APIs — REST, GraphQL, gRPC, and AsyncAPI patterns including pagination, versioning, error handling, rate limiting, and API governance. Use when the user asks to design APIs, create endpoints, build an API layer, write OpenAPI specs, or needs help with REST/GraphQL/gRPC service design.
api-design-first
Design-first API development skill. Generates OpenAPI 3.1 specifications, enforces REST design best practices, validates endpoints, handles versioning, pagination, error formatting, authentication patterns, rate limiting, and idempotency. Activates when users say "design an API", "create OpenAPI spec", "API endpoint"…
strapi-cms
Customisable headless CMS with Strapi.
api-design
Applies REST and GraphQL design principles to produce or review an API contract.
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
scalar-design-system
Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library. Use when designing or implementing Scalar UI, especially with Paper (code-to-design / design-to-code), so output matches real Scalar tokens, colors, typography, spacing, and components instead of…