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 paruff/uFawkesAI --skill ai-stancegit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/ai-stance)<a href="https://agentmods.dev/skills/paruff/ufawkesai/ai-stance"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/ai-stance/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/paruff/ufawkesai/ai-stance"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/ai-stance.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.00058 | $0.01709 |
| Opus 5 | $0.00029 | $0.00855 |
| Sonnet 5 | $0.00012 | $0.00342 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
ai-stance 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 12d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: AI Stance
Load trigger:
"load ai-stance skill"> DORA: AI Capability 1 (Clear and communicated AI stance) Token cost: Low
Purpose
Produce and maintain AI_STANCE.md — the document that gives every contributor
(human and agent) unambiguous clarity on how AI tools are used in this repo.
Ambiguity creates risk; clarity creates psychological safety for effective experimentation.
DORA AI Capabilities Model v2025.1 identifies four required clarity dimensions: expectation of use, organizational support, permitted tools, and role applicability. This skill ensures all four are present.
Three-Bucket Framework
Every AI_STANCE.md must classify all AI tool usage into exactly three buckets. No "it depends" without specifying what it depends on.
| Bucket | Definition | Decision rule |
|---|---|---|
| Prohibited | Never permitted in this repo, regardless of context | Safety, compliance, or trust boundary violated |
| Permitted with guardrails | Allowed when stated conditions are met | Default for most AI-assisted development |
| Allowed | No special conditions required | Low-risk, fully reversible, human-verifiable |
Default Stance for uFawkes* Repos
Pre-populated for the fawkes suite. Override per repo as needed.
Prohibited
- Sending PII, secrets, or proprietary infrastructure configs to public AI models
- Committing AI-generated code without running pre-commit hooks
- Bypassing branch protection rules because "the AI said it was fine"
- Using AI to generate security policy or compliance documentation without human expert review
- AI-generated content in Dojo modules without disclosure to learners
Permitted with Guardrails
What ships with it
3 files 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.
- 12d ago First seen · 186 lines · 58 tokens per session scan A 319f764b5b70
ai-stance is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 20d ago), licensed MIT. It adds 58 tokens to every session and 1,709 once invoked, about $0.0003 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
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
infrastructure-overview
Top-level skill for the research template infrastructure layer. Use in Cursor, Claude Code, or similar agents when editing or importing anything under infrastructure/, understanding the two-layer architecture, or wiring build/validation/rendering/publishing. Covers module discovery, import patterns, thin…
infrastructure-validation
Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.
infrastructure-llm
Skill for the LLM infrastructure module providing local Large Language Model integration via Ollama. Covers client initialization, prompt templates, output validation, manuscript review generation, conversation context, and CLI usage. Use when querying LLMs, generating manuscript reviews, validating LLM outputs, or…
research-workflow
Seven-stage research workflow (SCOPE→LITERATURE→REASON→DESIGN→COMPUTE→SYNTHESIZE→WRITE). Use for: structuring an AI agent's research process, generating literature review prompts, scoping methodology. Usage: from infrastructure.research import ResearchWorkflow; ResearchWorkflow.describe() Config: set stage overrides…
infrastructure-search-literature
Paperclip-style multi-source literature search across arXiv, Crossref, local JSON corpora, and (opt-in) the Paperclip API. Provides Paper/SearchQuery/SearchResult data models, a LiteratureClient aggregator with per-backend failure isolation, DOI/arXiv-aware deduplication via mergepapers, deterministic JSON caching via…