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 markoblogo/abvx-agent-skills --skill editorial-surfacegit clone --depth 1 https://github.com/markoblogo/abvx-agent-skillsWrote 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/markoblogo/abvx-agent-skills/editorial-surface)<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/editorial-surface"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/editorial-surface.svg" alt="Measured on agentmods" 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.00049 | $0.00613 |
| Opus 5 | $0.00024 | $0.00307 |
| Sonnet 5 | $0.00010 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
editorial-surface 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 8d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editorial Surface
Treat reading experience as a product requirement, not decorative polish.
Use this when the surface is text-first and the common failure mode is bad hierarchy, empty cards, oversized hero treatments, weak excerpt logic, or unreadable body rhythm.
Best Fit
- article pages;
- blog and writing indexes;
- guide pages;
- book and booklet landing sections;
- featured and recent content cards;
- mixed text/media editorial layouts.
Design Priorities
- title, deck, metadata, and body must read as one system;
- body measure and paragraph rhythm win over decorative hero treatment;
- cards should carry the right amount of information for their role;
- media should support reading, not interrupt it;
- text-only surfaces should still feel intentionally composed.
Workflow
- Identify the content role:
- index, featured card, recent card, article page, guide, or mixed editorial section.
- State the reading job:
- skim, choose, commit, or read deeply.
- Check the hierarchy:
- label/source/date;
- title;
- deck/excerpt;
- body;
- supporting media;
- actions and related links.
- Fix the common structural failures first:
- oversized title block;
- empty right side on text-only featured cards;
- recent cards with dead space instead of useful excerpt;
- metadata too faint to scan;
- body too light, narrow, or long-line;
- video or external resources placed without narrative rhythm.
- For mixed media, place media where it helps comprehension:
- not automatically adjacent to cover art if that creates a media wall;
- not after the entire article if it belongs near the core narrative.
- Verify desktop and mobile reading comfort before calling the change ready.
Output Shape
Return:
content rolereading jobhierarchy fixesexcerpt rulemedia placement ruledesktop/mobile reading checks
Guardrails
- Do not rewrite owner-approved article body unless explicitly asked.
- Do not turn editorial pages into generic marketing pages.
- Do not add decorative imagery to cover for weak hierarchy.
- Do not shrink content density so far that text-first surfaces become empty.
- Do not imitate Medium or Substack blindly when the project has its own identity.
What ships with it
2 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.
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.
- 8d ago First seen · 87 lines · 49 tokens per session scan A 2b4e0cda0e9d
editorial-surface is a skill published in the GitHub repository markoblogo/abvx-agent-skills (16 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 613 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
screenshot-sweep
Use whenever a screenshot is captured or supplied — a bug report, a Playwright capture, a design review, a "does this look right". Read the WHOLE image, not just the thing it was sent for: sweep it against the defect checklist below, file the findings, and add them to the todo list. When a defect is later reported…
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
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.
app-screenshot-debug
Drive the running termio app via AppleScript / System Events to reach a UI state (focus the window, click a sidebar project, a terminal pane, a control), capture a pixel-accurate screenshot of just that window, and read it back for visual analysis — for diagnosing layout / spacing / alignment / 'this looks ugly'…
trace
Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.
codex-agent
Use when you want a second-opinion review via Codex CLI, cross-verification after another agent implements changes, debugging help, or alternative implementation proposals. Requires Codex CLI to be installed and authenticated.