Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dkharlanau/agent-ready-web-profilenpx agentmods add skills/dkharlanau/agent-ready-web-profile/arwp-adaptive-upgradeWrote 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/dkharlanau/agent-ready-web-profile/arwp-adaptive-upgrade)<a href="https://agentmods.dev/skills/dkharlanau/agent-ready-web-profile/arwp-adaptive-upgrade"><img src="https://agentmods.dev/badge/skills/dkharlanau/agent-ready-web-profile/arwp-adaptive-upgrade/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/dkharlanau/agent-ready-web-profile/arwp-adaptive-upgrade"><img src="https://agentmods.dev/badge/skills/dkharlanau/agent-ready-web-profile/arwp-adaptive-upgrade.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.00077 | $0.00748 |
| Opus 5 | $0.00039 | $0.00374 |
| Sonnet 5 | $0.00015 | $0.00150 |
| Haiku 4.5 | $0.00008 | $0.00075 |
Grade A, and why
arwp-adaptive-upgrade 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 3d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ARWP Adaptive Upgrade
Use this skill after or together with the Growth Loop when the user expects concrete changes to a target website.
Goal
Translate current evidence into:
site state → applicable practice → exact target → change recipe → verification → measurement → review
Do not emit a generic 0–100 GEO score.
Workflow
- Identify the target site's real vertical(s) and goals. Do not classify a normal site as
research-datasetunless a genuine reusable/distributable corpus exists. - Run or reuse the Growth Plan and vertical evidence.
- Compile the Adaptive Upgrade Graph:
node bin/arwp-upgrade.mjs site https://example.com/ \
--vertical=<vertical> \
--goals=search,generative-search,ai-citations,measurement
or:
node bin/arwp-upgrade.mjs compile arwp-growth.json \
--verticals=<verticals> \
--goals=<goals> \
--output=arwp-upgrade.json
- Review
knowledgeState. Anyreview-duepack must have its upstream primary source rechecked before implementation. - Work in dependency/priority waves. Fix P0 eligibility before optional acquisition or experimental agent surfaces.
- Respect the automation class:
mechanical: deterministic change may be suitable for bounded automation after authorization;grounded-template: fill only facts already verified in the target repository/site;policy-gated: require publisher decision;editorial: do not manufacture expertise, experience, claims or data;owner-platform: require authenticated platform evidence;runtime: require browser/task evaluation.
- For repository implementation, record the exact files/surfaces changed and run the site's own tests/build plus the recommendation verification contract.
- After verification, capture owner/runtime outcome evidence separately. Never treat a successful implementation check as proof of ranking or citation impact.
- Keep/revise/revert/retire the recommendation and preserve negative results.
Dataset activation
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.
- 3d ago First seen · 78 lines · 77 tokens per session scan A dff6dbfc65b9
arwp-adaptive-upgrade is a skill published in the GitHub repository dkharlanau/agent-ready-web-profile (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 748 once invoked, about $0.0004 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-08.
Other skills, from other repositories
hephaestus-network
Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until explicit completion.
routing-card-authoring
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.
hephaestus-upload
Use when the user types $hephaestus-upload, /hep-upload, or /agentlas-upload, or asks to upload, publish, or list an Agentlas agent or team. Ask Cloud (private) vs Agentlas Hub (public) FIRST, then publish through the bundled Hephaestus gate.
hep-network
Staff a task from registered Local, owner Cloud, and public Hub agents.
hep-upload
Upload an Agentlas agent after asking Cloud vs Hub first.
session-agent-builder
Turn the current interactive conversation into an owner-reviewed reusable Agentlas agent; accept JSON or JSONL only for explicit terminal and automation runs.