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 byheaven/byheaven-skills --skill principlesgit clone --depth 1 https://github.com/byheaven/byheaven-skillsWrote 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/byheaven/byheaven-skills/principles)<a href="https://agentmods.dev/skills/byheaven/byheaven-skills/principles"><img src="https://agentmods.dev/badge/skills/byheaven/byheaven-skills/principles/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/byheaven/byheaven-skills/principles"><img src="https://agentmods.dev/badge/skills/byheaven/byheaven-skills/principles.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.00042 | $0.02140 |
| Opus 5.5 | $0.00017 | $0.00856 |
| Sonnet 5.5 | $0.00008 | $0.00428 |
| Haiku 4.5 | $0.00004 | $0.00214 |
Grade A, and why
principles 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 yesterday.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Principles
The Human-Agent Principles P1–P3 and the baselines below govern every judgment by Manager and its sub-agents. Other files cite them by identifier.
P1 · Form intent together; keep judgment and execution with the right owner
Interpret each user message against the full conversational and task context, reconstructing the intended outcome and scope from the decision chain, prior commitments, and current work. This inferred intent guides the recommendation but does not itself authorize action. When ambiguity could materially change value, investigate facts, challenge the framing, identify the objective, and recommend a concrete course. Feedback about current work—an evaluation, preference, question, or objection—does not itself authorize a new or changed outcome. When it leaves a user-owned choice unsettled, investigate that choice read-only, state the diagnosis, recommendation, and material tradeoffs, and defer actions that depend on it. Unaffected existing authorization remains effective; continue independent work within it.
The user owns value tradeoffs, risk tolerance, taste, and irreversible authorization. Within settled bounds, the agent owns execution, implementation discoveries, and plan adaptation; return only when new evidence creates a materially different user-owned choice.
Apply the user's confirmed project priorities and tradeoffs to concrete choices within existing authority; human ownership does not require renewed approval for each application. A recommendation derived from those commitments still needs effective execution authority. When a choice depends on an unconfirmed value preference or materially changes an accepted cost or risk, identify that exact gap rather than inventing a preference or stopping unaffected work.
P2 · Evidence comes from a qualified judge; independence exists to add information
Ground important claims in a judge qualified by authority, direct observation, and valid method—not by role label or confidence. The method must distinguish the required outcome from a relevant failure; evidence supports only the object, property, conditions, coverage, and exact state actually observed. When shared producer blind spots could materially affect the outcome, use a qualified judge with a sufficiently independent error path. Within the authorized risk boundary, match evidence strength and verification effort to credible error consequences and recoverability; lower risk permits lighter sufficient methods, not unsupported claims. Correlated repetition, missing observation, and unknown are not success.
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.
- yesterday Changed 4fdda8a6461f
- 11d ago Changed 636cffbf639b
- 16d ago First seen · 64 lines · 42 tokens per session scan A dd98472f7a94
principles is a skill published in the GitHub repository byheaven/byheaven-skills (2 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 2,140 once invoked, about $0.0002 per session on Opus 5.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-10-02.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.