site-map-readiness

site-map-readiness is a skill for Codex from Eliyce/paqad-ai. It costs 40 tokens per session (587 once invoked), scanned A, original, MIT.

A readiness check for a site map, which is a structured description of an application's screens and flows. It detects the app type and frameworks, then checks whether the project has a suitable extractor.

In plain words
What is it for?
Use it at the start of a site-mapping run to decide whether extraction and modeling can proceed.
Why use it?
It prevents later mapping steps from running when the project cannot be understood by the available tools. It also clearly marks cases that are only partly supported or blocked.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it at the start of a site-mapping run to decide whether extraction and modeling can proceed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/eliyce/paqad-ai/site-map-readiness
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 Eliyce/paqad-ai --skill site-map-readiness
Clone the repo
git clone --depth 1 https://github.com/Eliyce/paqad-ai

Made for: 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.

agentmods badge for site-map-readiness

README.md
[![agentmods](https://agentmods.dev/badge/skills/eliyce/paqad-ai/site-map-readiness/github.svg)](https://agentmods.dev/skills/eliyce/paqad-ai/site-map-readiness)
Your own site
<a href="https://agentmods.dev/skills/eliyce/paqad-ai/site-map-readiness"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/site-map-readiness/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.

agentmods 80×15 button for site-map-readiness

Your own site · 80×15
<a href="https://agentmods.dev/skills/eliyce/paqad-ai/site-map-readiness"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/site-map-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 587 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00587
Opus 5 $0.00020 $0.00293
Sonnet 5 $0.00008 $0.00117
Haiku 4.5 $0.00004 $0.00059

Measured 8d ago against content hash 5a621ace990d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

site-map-readiness 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.

runtime/capabilities/coding/skills/site-map-readiness/SKILL.md · 67 lines

How it starts

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

What It Does

Confirms the project is mappable before the workflow spends any effort: the app kind and frameworks are detectable, and at least one extractor covers the app's shape. Emits a readiness verdict (ready | partial | blocked) that gates everything downstream. Runs first, like design-system-coverage gates the design-test workflow.

Use This When

Use this as the first skill in every site-map run. Never run extraction, modeling, or verification without a ready or partial verdict from it.

Inputs

  • Read .paqad/project-profile.yaml for the detected active_capabilities and stack_profile.
  • Read the project manifests the profile points at (package.json, composer.json, lockfiles).
  • Read references/readiness-criteria.md before grading.

Procedure

The verdict is a deterministic function of what the engine can detect — drive it from the engine, do not re-derive detection in prose.

  1. Run paqad-ai sitemap run and read the readiness and blocked_checks it reports; the engine owns app-kind and framework detection.
  2. Grade the verdict: ready when an extractor covers the app shape, partial when only the generic convention fallback applies, blocked when no extractor covers the shape.
  3. Emit the readiness inventory (app kind, frameworks, extractor, verdict, blocked reasons).

Output Contract

  • A JSON object { app_kind, frameworks: [...], extractor, verdict, blocked_checks: [...] }.
  • verdictready | partial | blocked.
  • A blocked verdict must carry at least one blocked_checks entry with a reason.

Escalate / Stop Conditions

  • Stop when the verdict is blocked: surface the engine's blocked_checks reason and do not fabricate surfaces to fill the gap.
  • Warn when the verdict is partial: downstream skills run in exploratory mode and tag surfaces confidence: low.
  • Do not upgrade a partial verdict to ready to unblock the run.

Resources

  • references/readiness-criteria.md
  • agents/openai.yaml

Read the full file on GitHub · 67 lines

Files

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.

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.

  1. 8d ago First seen · 67 lines · 40 tokens per session scan A 5a621ace990d

Subscribe to this mod's changes

site-map-readiness is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 587 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-09-03.