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 agentmods add skills/aave/aave-v4-sdk/publishnpx skills add aave/aave-v4-sdk --skill publishgit clone --depth 1 https://github.com/aave/aave-v4-sdkWrote 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/aave/aave-v4-sdk/publish)<a href="https://agentmods.dev/skills/aave/aave-v4-sdk/publish"><img src="https://agentmods.dev/badge/skills/aave/aave-v4-sdk/publish.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.00019 | $0.00635 |
| Opus 5 | $0.00010 | $0.00318 |
| Sonnet 5 | $0.00004 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
publish 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 6d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish SDK Packages
Publishes @aave packages to npm using changesets.
Checklist
You MUST use TodoWrite to create a todo for EACH step below. Mark each complete only after verification.
Pre-flight
- Verify on
mainbranch and up-to-date:git checkout main && git pull - Verify working directory is clean:
git statusshows no uncommitted changes - Run
nvm useto ensure correct Node.js version - Run
corepack enableto ensure correct pnpm version - Run
pnpm installto update dependencies - Run
pnpm buildto build all packages
Version Bump
- Run
pnpm changeset:statusto check for pending changesets (if none exist, nothing to publish - STOP) - Run
pnpm changeset:versionto bump versions - Review output: if in pre-release mode and "major" bumps appear, ask user to confirm
- Stage and commit:
git add . && git commit -m "chore: bumps up versions"
Publish
- Verify npm authentication: run
pnpm whoami- If it fails: ask user to run
pnpm loginthen re-verify
- If it fails: ask user to run
- Ask user for npm OTP code (from authenticator app)
- Run
NPM_CONFIG_OTP=<otp> pnpm changeset:publishwith the provided OTP- If OTP expires mid-publish: ask for new OTP and retry failed packages manually
- If publish fails partially: check npm for which packages published, may need manual recovery
- Run
git push --follow-tags
Stop Conditions
| Condition | Action |
|---|---|
| Not on main branch | git checkout main && git pull first |
| Uncommitted changes | Stash or commit first |
| Tests failing | Fix tests before publishing |
pnpm changeset:status shows no changesets |
Nothing to publish - inform user |
pnpm whoami fails |
User must run pnpm login |
| Major bump in pre-release mode | Confirm with user - may be unintentional |
Pre-release Mode
When .changeset/pre.json exists:
- Packages publish with
-next.Nsuffix (e.g.,4.1.0-next.16) - Major version bumps should be rare - verify intentional
- The
tagfield inpre.jsonshows the npm dist-tag (next)
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.
- 6d ago First seen · 63 lines · 19 tokens per session scan A cf0e6c035210
publish is a skill published in the GitHub repository aave/aave-v4-sdk (24 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 635 once invoked, about $0.0001 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…