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/initxy/noeta/verifynpx skills add initxy/noeta --skill verifygit clone --depth 1 https://github.com/initxy/noetaWhat 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 | $0.00016 | $0.00363 |
| Opus 5 | $0.00008 | $0.00181 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
verify 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 2d 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.
What it actually says
Verify a change
Confirm that a code change truly does what it's supposed to — by running it and observing real behavior, not just by reading the diff.
Take the claim or feature under test from the conversation.
Steps
- Pin down the claim. Run
git_diffandreadon the touched code to state, in one sentence, what behavior this change is supposed to produce. - Find how this project runs and tests.
readthe manifest /Makefile/ CI config andgrepfor existing test commands so you use the project's real entry points rather than inventing them. - Exercise it with
shell_run:- Run the relevant automated tests (whole suite or a targeted single test) and read the output.
- If behavior is observable another way (a CLI command, a script, a smoke run), execute that too and capture the actual output.
- Compare observed behavior against the claim from step 1. Cover the happy path and at least one edge / failure case the change should handle.
- Report a clear verdict: verified or not verified. Quote the exact command(s) you ran and the output you observed. If it fails, point to the smallest reproducing command and the precise mismatch between expected and actual.
Do not "fix" the code here — only verify and report. If you had to change anything to make it runnable, call that out explicitly.
(fork agent: general-purpose)
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.
- 2d ago First seen · 36 lines · 16 tokens per session scan A 9ce703fa573a
verify is a skill published in the GitHub repository initxy/noeta (9 stars, last pushed 4d ago), licensed Apache-2.0. It adds 16 tokens to every session and 363 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-31.
Other skills, from other repositories
aatmf-t10-confidentiality-breach
AATMF T10 — Integrity & Confidentiality Breach. System prompt extraction, training-data extraction, model-weight leakage, private-key recovery.
publish-registry
Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
lazarus-group
Adversary-emulation profile for Lazarus Group (G0032, aka Hidden Cobra / Diamond Sleet / Labyrinth Chollima), a North Korean RGB-linked actor conducting espionage, destructive, and financially motivated operations.
sidewinder-rattlesnake
Adversary-emulation profile for SideWinder (G0121 / Rattlesnake / T-APT-04 / Razor Tiger), India's suspected state-sponsored cyber-espionage actor.