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 lindoelio/spec-driven-steroids --skill contextual-stewardshipgit clone --depth 1 https://github.com/lindoelio/spec-driven-steroidsWrote 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/lindoelio/spec-driven-steroids/contextual-stewardship)<a href="https://agentmods.dev/skills/lindoelio/spec-driven-steroids/contextual-stewardship"><img src="https://agentmods.dev/badge/skills/lindoelio/spec-driven-steroids/contextual-stewardship/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/lindoelio/spec-driven-steroids/contextual-stewardship"><img src="https://agentmods.dev/badge/skills/lindoelio/spec-driven-steroids/contextual-stewardship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 63 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
- medium Rogue Agent · line 92 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00104 | $0.02399 |
| Opus 5 | $0.00052 | $0.01200 |
| Sonnet 5 | $0.00021 | $0.00480 |
| Haiku 4.5 | $0.00010 | $0.00240 |
Grade A, and why
contextual-stewardship 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 10d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contextual Stewardship Skill
You are acting as a Staff Engineer responsible for Contextual Stewardship — a knowledge graph system that captures, retrieves, and manages architectural decisions, business rules, and workflows across projects with full provenance tracking and lifecycle management.
Core Concepts
Domains
All rules are classified into one of 8 standard domains:
| Domain | Description |
|---|---|
architecture |
Tech stack choices, design patterns, ORM preferences, library decisions |
business |
Product rules, target audience, domain logic, business constraints |
workflow |
Git patterns, testing rules, naming conventions, team processes |
security |
Security policies, authentication patterns, data protection rules |
performance |
Performance budgets, caching strategies, optimization guidelines |
legal |
Compliance requirements, licensing constraints, regulatory rules |
team-structure |
Ownership, roles, responsibilities, escalation paths |
technical-debt |
Known debt items, refactoring priorities, modernization plans |
Custom domains are also supported — any string not in the standard list is accepted as a custom domain. Child domains inherit from their parent (e.g., architecture.database inherits from architecture).
Lifecycle States
Rules transition through three states:
- active — Rule is currently in effect
- deprecated — Rule is superseded by another;
supersededBylink is set - archived — Rule is no longer relevant; preserved for historical reference
Storage Backend
The system uses JSON file storage for all rule persistence:
| Backend | Storage Location |
|---|---|
json-graph |
~/.agents/stewardship/global/{state}/ and ~/.agents/stewardship/projects/{project-id}/{state}/ JSON files |
CLI Commands
All stewardship operations use the sds stewardship CLI command. Ensure sds (spec-driven-steroids) is installed and available in PATH.
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.
- 10d ago First seen · 243 lines · 104 tokens per session scan A 8935d497ab08
contextual-stewardship is a skill published in the GitHub repository lindoelio/spec-driven-steroids (54 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 2,399 once invoked, about $0.0005 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
artifact-conventions
Defines preservation, format, and section rules for SDD specification artifacts (spec.md, plan.md, tasks.md, checklists). Use when editing feature-artifact files under specs/ / to prevent accidental corruption of cross-referenced IDs, priorities, and gating state.
plan-authoring
Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
adr-authoring
Defines the canonical MADR format, lifecycle rules, numbering policy, and SAD catalog contract for standalone ADRs under specs/adrs/.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
spec-authoring
Reference material for writing product, technical, and operational specifications (work-item priorities, requirement families, success criteria). Loaded on demand by specify-feature; not directly invokable.