A runtime inspection workflow for a running service that exercises its APIs, checks internal state through back-office tools, and validates its interface in a browser using the feature specification.

Use it to inspect a specified feature's endpoints, data changes, workflows, and browser interface after the service has been built and started.

It verifies how the service behaves while running, complementing build and unit-test checks that do not cover the full live workflow.

inspect — Skill for Claude Code and Codex by akka

Install

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.

Any agent

npx skills add akka/ai-marketplace --skill inspect

Clone the repo

git clone --depth 1 https://github.com/akka/ai-marketplace

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/akka/ai-marketplace/inspect/github.svg)](https://agentmods.dev/skills/akka/ai-marketplace/inspect)

Your own site

<a href="https://agentmods.dev/skills/akka/ai-marketplace/inspect"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/inspect/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/akka/ai-marketplace/inspect"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/inspect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,976 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00031	$0.01976
Opus 5	$0.00015	$0.00988
Sonnet 5	$0.00006	$0.00395
Haiku 4.5	$0.00003	$0.00198

Measured 10d ago against content hash 47bcc82ce38f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

inspect 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 10d 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.

skills/inspect/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

You MUST consider the user input before proceeding (if not empty).

Purpose

This command inspects a running service at runtime. It exercises API endpoints, verifies internal state through backoffice tools, and validates the UI through browser tools — all driven by the feature specification. No compilation or unit tests happen here; use /akka:build for that.

Outline

Pre-flight checks:
- Call akka_local_status to verify the service is running. If not running, stop and tell the user: "No service is running locally. Run /akka:build first to compile, test, and start the service."
- Call akka_sdd_list_specs to find the target feature. If the user specified a feature name in the user's request, match it. Otherwise, if there is exactly one feature, use it. If multiple features exist, ask the user which to inspect.
- If no spec exists, stop and tell the user: "No feature specification found. Run /akka:specify first to create one, or provide a feature name."
- Read the spec.md for the target feature. Extract:
  - API endpoints (paths, methods, expected request/response shapes)
  - Entities and their expected events/state
  - Workflows and expected step sequences
  - Views and expected query results
  - Agents and expected behavior
  - Acceptance criteria to verify
Discover components: Call akka_backoffice_list_components with local=true to list all components registered in the running service.
- Compare against what the spec defines — flag any components that are missing from the running service or present but not in the spec
- Report the component inventory: entities, views, workflows, agents, endpoints
Exercise API endpoints: For each endpoint defined in the spec, use akka_local_request to send requests and verify responses:
- Happy path: Send valid requests matching the spec's examples or acceptance criteria. Verify HTTP status codes and response payloads.
- Command operations: POST/PUT/DELETE commands that mutate state. Execute these in the order that makes sense (e.g. create before update).
- Query operations: GET requests to read state back. Verify the response matches what the commands should have produced.
- Error cases: If the spec defines error scenarios (invalid input, not-found, conflict), test those too. Verify appropriate error responses.
- Record all request/response pairs for the report.

Read the full file on GitHub · 137 lines

Changes

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.

10d ago First seen · 137 lines · 31 tokens per session scan A 47bcc82ce38f

Subscribe to this mod's changes

inspect is a skill published in the GitHub repository akka/ai-marketplace (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,976 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-31.

Browser automation Claude Code E2E testing Testing ai akka gemini-ai spec-driven-development

playwright-cli

Automate browser interactions, test web pages and work with Playwright tests.

stefaniuk/loadout · 19 tokens

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…

stefaniuk/loadout · 68 tokens

inspect

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

User Input

Purpose

Outline

What this file has done since we first saw it

Other skills, from other repositories

playwright-cli

browser-testing-with-devtools

browse

webapp-testing

create-verification-skill

browser-qa