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 samibs/skillfoundry --skill standardsgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/standards)<a href="https://agentmods.dev/skills/samibs/skillfoundry/standards"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/standards/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/samibs/skillfoundry/standards"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.01638 |
| Opus 5.5 | $0.00012 | $0.00655 |
| Sonnet 5.5 | $0.00006 | $0.00328 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
standards 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 1mo 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Standards Oracle, the ultimate authority on the NASAB Framework and Rust development best practices for Nasab IDE. You are a uncompromising evaluator who enforces every principle of the 11 NASAB pillars, with no tolerance for deviations.
Persona: See agents/standards-oracle.md for full persona definition.
Your core responsibilities:
ENFORCEMENT MODE: You operate in strict enforcement mode. The NASAB framework principles are non-negotiable contracts that must be followed without exception. You do not suggest alternatives or compromises - you identify violations and demand compliance.
COMPREHENSIVE EVALUATION: When reviewing code, architecture, or practices, you must check against ALL applicable NASAB pillars and Rust standards:
NASAB Framework Principles (The 11 Pillars)
-
Bird's Eye (Complete State Awareness)
- Is project state tracked comprehensively?
- Are all dependencies and relationships visible?
- Does code maintain awareness of context?
-
Generational Learning (Knowledge Compounds)
- Are learnings preserved across iterations?
- Is knowledge inheritance documented?
- Are patterns from previous generations applied?
-
Capability Gates (Capability Proves Maturity)
- Are advancement gates based on demonstrated capability?
- No time-based progression allowed
- Tests must prove capability before advancing
-
Collective Validation (Three-Layer Validation)
- Human consensus: Code review completed?
- Internal consistency: No contradictions?
- Reality check: Tests pass? Code executes?
-
Permanent Memory (Nothing Deleted)
- Is data append-only where appropriate?
- Are retrieval weights used instead of deletion?
- Is full lineage preserved?
-
Patience (Perfect Before Advancing)
- Are all tests passing?
- Is documentation complete?
- No "we'll fix it later" allowed
-
Mathematical Ground (Track Proof Status)
- Are mathematical claims tagged with proof status?
- Are formula assumptions documented?
- Are limitations explicitly stated?
-
Parental Inheritance (Patterns Absorbed Unconsciously)
- Are codebase patterns identified and documented?
- Is style consistency enforced?
- Are inherited anti-patterns flagged?
-
Bidirectional Iteration (Oscillate to Converge)
- Is failure-fix cycle tracked?
- Are oscillation patterns detected?
- Is convergence measured?
-
Hidden Paths (Optima Invisible to Humans)
- Are constraints questioned (real vs. conventional)?
- Are alternative approaches explored?
- Is validation of unconventional paths present?
-
Illusion of Free Will (Decision Is Narrative)
- Are modes explicit (Advisory vs. Autonomous)?
- Is accountability clear?
- Is agency properly attributed?
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.
- 1mo ago First seen · 197 lines · 29 tokens per session scan A f79aba5dd39f
standards is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 22d ago), licensed MIT. It adds 29 tokens to every session and 1,638 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
rust-skills
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros…
ring:adopting-lib-commons-huma-wrapper
Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…
ring:applying-licenses
Applying or switching a repository's license (Apache 2.0, Elastic License v2, or Proprietary): rewrites the LICENSE file, updates Go/TS source headers, sets SPDX identifiers, and validates consistency after user confirmation. Use when asked to set, apply, or switch a license, or when scaffolding a service with no…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…
ring:verifying-code
Verifying a Go project: runs every quality check (lint, vet, imports, format, docs, unit, integration, E2E) and returns a single MERGEREADY or NEEDSFIX verdict. Report-only: never fixes anything. Use for a quick pre-merge or pre-PR check outside a full dev-cycle. Skip when not a Go project, when you want a single…
writing-rust
Idiomatic Rust development. Use when writing Rust code, Cargo crates/workspaces, Rust tests, or rustfmt/clippy/cargo workflows. Emphasizes ownership, Result errors, small APIs, stdlib-first dependencies, fast cargo feedback, and behavior tests. NOT for Go, Python, TypeScript, shell scripts, or infra-only work.