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 rakutentech/sorify --skill sorify-recordinggit clone --depth 1 https://github.com/rakutentech/sorifyWrote 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/rakutentech/sorify/sorify-recording)<a href="https://agentmods.dev/skills/rakutentech/sorify/sorify-recording"><img src="https://agentmods.dev/badge/skills/rakutentech/sorify/sorify-recording/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/rakutentech/sorify/sorify-recording"><img src="https://agentmods.dev/badge/skills/rakutentech/sorify/sorify-recording.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.00223 |
| Opus 5.5 | $0.00010 | $0.00089 |
| Sonnet 5.5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
sorify-recording 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.
What it actually says
Generate from a recording
Use this skill when the user asks to generate a test from a Sorify Recorder session.
- Confirm the
sorify-recorderMCP server is connected and resolve the requested recording, using the newest recording forlatest. - If the recorder binary is unavailable, explain that it must be installed
at
~/.sorify-bin/sorify-recorder-mcpand that the browser extension must be loaded. - Read the recording metadata and present a numbered interpretation of the actions. Do not create anything in Sorify until the user confirms.
- After confirmation, generate the replay test, upload relevant stop-phase cookies when requested, create the suite/test, trigger the run, and report the result.
For the full event-field reference, cookie handling, confirmation gate, and
test-generation rules, read ../../commands/recording.md.
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 · 24 lines · 25 tokens per session scan A 663cc2ac38f3
sorify-recording is a skill published in the GitHub repository rakutentech/sorify (50 stars, last pushed 4d ago), licensed Apache-2.0. It adds 25 tokens to every session and 223 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-16.
Other skills, from other repositories
release-qa
Test an AI-built web app like a senior QA engineer before release. Use when the user asks to test, QA, verify, ship, check regressions, inspect a browser flow, or decide whether a web app is ready to launch.
ui-test-cypress
Use this skill when you need to design Cypress e2e and component testing plans with commands, fixtures, network stubbing, and CI reporting; triggers include Cypress UI testing, UI automation testing, and ui-test-cypress.
ui-test-playwright
Use this skill when you need to design Playwright Test suites with fixtures, projects, traces, screenshots, API plus UI coverage, and CI reporting; triggers include Playwright UI testing, UI automation testing, and ui-test-playwright.
ui-test-puppeteer
Use this skill when you need to design Puppeteer automation for Chromium-driven checks, screenshots, PDFs, network interception, and CDP use cases; triggers include Puppeteer UI testing, UI automation testing, and ui-test-puppeteer.
ui-test-selenium
Use this skill when you need to design Selenium WebDriver UI automation plans with stable locators, waits, Page Objects, Grid, and CI execution; triggers include Selenium UI testing, UI automation testing, and ui-test-selenium.
ui-test-testcafe
Use this skill when you need to design TestCafe UI automation with fixtures, selectors, roles, browser matrix execution, and reports; triggers include TestCafe UI testing, UI automation testing, and ui-test-testcafe.