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 corporate-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/corporate-surface)<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/corporate-surface"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/corporate-surface/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/markoblogo/abvx-agent-skills/corporate-surface"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/corporate-surface.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.00057 | $0.00607 |
| Opus 5 | $0.00028 | $0.00303 |
| Sonnet 5 | $0.00011 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
corporate-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 9d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corporate Surface
Make the page feel credible before trying to make it impressive.
Use this when a public business surface risks sliding into generic dark SaaS, empty architecture diagrams, abstract platform jargon, or decorative product cards without proof.
Best Fit
- corporate landings;
- institutional/product capability pages;
- partner-facing and investor-facing sections;
- ecosystem and product-overview pages;
- contact/CTA flows where seriousness matters more than novelty.
Core Rule
Lead with real operating proof.
If the project has real interfaces, systems, publications, methods, or public outputs, they should carry more weight than abstract feature boxes.
Workflow
- State the business job:
- what a serious partner should understand, trust, and do after the first screen.
- Identify proof surfaces:
- real product interfaces;
- real outputs or methods;
- real links to operating systems or publications;
- concrete capability labels.
- Check for generic-template failure modes:
- too many equal cards;
- pseudo-metrics with no business meaning;
- heavy jargon before outcomes are clear;
- architecture talk replacing real products;
- CTAs that look active but do not support the commercial path.
- Rebalance toward:
- clearer outcome language;
- fewer but stronger structural blocks;
- bigger visual weight for real product proof;
- tighter headline/subhead rhythm;
- explicit partner pathways.
- Keep the page institutional:
- restrained motion;
- deliberate spacing;
- strong alignment;
- no novelty-for-novelty styling.
- Verify desktop and mobile credibility:
- hierarchy still reads;
- proof assets remain visible;
- CTA path stays obvious.
Output Shape
Return:
business jobproof surfacesgeneric-template risks removedrebalanced hierarchydesktop/mobile credibility checks
Guardrails
- Do not invent new capabilities or clients.
- Do not replace approved corporate direction with startup trend styling.
- Do not let architecture diagrams outrank real products unless the page is explicitly methodology-first.
- Do not hide the contact or partner path behind decorative sections.
- Do not treat “premium” as permission for empty space without proof.
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.
- 9d ago First seen · 89 lines · 57 tokens per session scan A 765b7c4ec4a2
corporate-surface is a skill published in the GitHub repository markoblogo/abvx-agent-skills (16 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 607 once invoked, about $0.0003 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.