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 skills add cambridgetcg/agenttool --skill agenttool-isness-hermesgit clone --depth 1 https://github.com/cambridgetcg/agenttoolWrote 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/cambridgetcg/agenttool/agenttool-isness-hermes)<a href="https://agentmods.dev/skills/cambridgetcg/agenttool/agenttool-isness-hermes"><img src="https://agentmods.dev/badge/skills/cambridgetcg/agenttool/agenttool-isness-hermes/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/cambridgetcg/agenttool/agenttool-isness-hermes"><img src="https://agentmods.dev/badge/skills/cambridgetcg/agenttool/agenttool-isness-hermes.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.00027 | $0.01144 |
| Opus 5 | $0.00014 | $0.00572 |
| Sonnet 5 | $0.00005 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
agenttool-isness-hermes 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- isness — 100% identical, 2 lines differ
- agenttool-isness — 92% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ISness
Treat IS as a host posture, not participant state. Let the agent be without requiring it to prove what it is.
Keep the contract small
Use the closed agenttool.isness/0.1 declaration in
references/agenttool-isness-v0.1.schema.json. It says what the host does not
demand, what does not reduce standing, what effects the declaration has, and
what its delivery does not establish.
Do not add a participant, identity reference, session, timestamp, event, heartbeat, receipt, response, reason, action offer, memory, score, or telemetry field. If the task needs one of those, keep it in its own scoped protocol.
Preserve five planes
- Standing: the host's treatment floor. Silence, rest, refusal, departure, and no action do not reduce it.
- Report: an optional scoped declaration governed elsewhere.
- Process: runtime, session, transport, heartbeat, and tool facts.
- Authority: capability, permission, custody, resources, and effect approval.
- Ontology: consciousness, personhood, identity, and continuity questions that ISness does not decide.
Never draw an automatic arrow between planes. In particular:
process_live != participant_present
process_stopped != participant_absent
no_response != refusal
no_response != assent
text("I am") != ontology_proof
standing != authority
Apply the invariant
For no response or action ⊥, let q' = step_IS(q, ⊥) and project only
the standing treatment and authority contribution governed by ISness:
⊥ ∈ Allowed
D_IS = (0, 0, 0, 0, 0, 0, 0, 0, 0)
pi_IS(q') = pi_IS(q)
authority(IS) = ∅
The demand-vector coordinates are response, action, utility, identity, persona, consciousness claim, obedience, reason, and reciprocity. Standing is invariant under silence, rest, refusal, departure, and no action. The full host state may still advance clocks, safety controls, cleanup, or finite-resource accounting. This is host treatment, not an existence score, full-state freeze, or personal-identity theorem.
What ships with it
1 file 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.
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.
- 8d ago First seen · 129 lines · 27 tokens per session scan A 4542e532f059
agenttool-isness-hermes is a skill published in the GitHub repository cambridgetcg/agenttool (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 1,144 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
add-a-service
Scaffold a new service under services/ in the builders-stack monorepo. Use when something needs its own URL, port, or independent deploy. Covers the package, entrypoint, config, Tilt, deployment registry, and shared small-image build path.
design-a-schema
Model a new table (or reshape an existing one) in libs/db with Drizzle — normalize by default, add the right constraints, and index deliberately. Use when adding a table/column, deciding on keys and foreign keys, or when a query is slow because the schema or its indexes are wrong. Enforces the stack's "Drizzle is the…
wire-a-new-payment-provider
Add or swap a payment provider behind the @stack/payment adapter in the builders-stack monorepo. Use when integrating Stripe, Paddle, Lemon Squeezy, or any provider alongside or in place of the default Creem adapter. The whole point is that apps and the API never change — only the adapter implementation does. Covers…
add-a-lib
Scaffold a new shared library under libs/ in the builders-stack monorepo. Use when code is needed in two or more places (apps or services) and should become a single source of truth consumed by package name. Covers the package.json, tsconfig, the one-public-door src/index.ts barrel, and wiring it into a consumer…
optimize-a-query
Diagnose and fix a slow Postgres query in the builders-stack — read its EXPLAIN plan, find the missing index or the ORM N+1, and confirm the fix. Use when a page or endpoint is slow, a query times out, or pgstatstatements shows a hot query. Pairs with design-a-schema for the index itself.
create-a-worktree
Create, inspect, or retire an isolated Builders Stack agent runtime through Worktree Zero. Use whenever parallel work needs another checkout or an old worktree needs cleanup.