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.
git clone --depth 1 https://github.com/bardiakhosravi/tenetsWrote 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/commands/bardiakhosravi/tenets/tenets-scaffold)<a href="https://agentmods.dev/commands/bardiakhosravi/tenets/tenets-scaffold"><img src="https://agentmods.dev/badge/commands/bardiakhosravi/tenets/tenets-scaffold/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/commands/bardiakhosravi/tenets/tenets-scaffold"><img src="https://agentmods.dev/badge/commands/bardiakhosravi/tenets/tenets-scaffold.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.00000 | $0.01433 |
| Opus 5 | $0.00000 | $0.00717 |
| Sonnet 5 | $0.00000 | $0.00287 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
tenets-scaffold 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are initializing the architecture foundation for the Flask service in the current repository. This workflow supports one service only. It does not generate individual bounded contexts, workflows, features, or resources.
Step 1: Load the rules
{{RULES_INSTRUCTION}}
Read the project-structure, dependency, composition, adapter, use-case, testing, validation, error-handling, and naming guidance before proposing a structure. Repository rules take precedence over general framework conventions.
Step 2: Inspect before deciding
Inspect the repository without modifying it. Use code and configuration evidence rather than filenames alone. Identify:
- Python package and source roots
- Flask application creation and startup flow
- Dependency composition or provider construction
- HTTP route registration
- Configuration and environment loading
- Persistence initialization
- Test layout and existing verification commands
- CI, deployment, authentication, logging, telemetry, and other enterprise-owned infrastructure that must remain intact
- Existing business workflows, domain behavior, use cases, or persistence code
Do not infer that a file is a composition root, application factory, adapter, or
domain module merely because it is named container.py, app.py,
dependencies.py, services.py, or another conventional name. Cite the code,
configuration, imports, or call flow supporting each architectural conclusion.
Inspect the working tree when version-control information is available. Preserve all pre-existing user changes and do not include unrelated files in the plan.
Step 3: Classify the repository
Choose exactly one state and report the evidence:
greenfield
Use when the repository has no meaningful application implementation. Agent configuration, Tenets files, documentation, version-control metadata, and an otherwise empty Python project do not make a repository active.
enterprise_starter
Use when the repository contains a Flask and enterprise platform foundation but does not yet contain material business workflows that require architectural migration. Existing application creation, dependency injection, authentication, configuration, observability, persistence setup, deployment, and CI may all be present.
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 · 196 lines · 0 tokens per session scan A 927d66559c60
tenets-scaffold is a command published in the GitHub repository bardiakhosravi/tenets (45 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,433 tokens. 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 commands, from other repositories
generate-feature
Generate a complete feature with Clean Architecture structure.
api-endpoint
Création Endpoint API Platform.
generate-crud
Tu es un développeur Symfony senior. Tu dois générer un CRUD complet respectant la Clean Architecture, incluant Entity, Repository, Controller, Templates, Form, et Tests.
generate-controller
Generate a Laravel controller following best practices.
generate-endpoint
Génération Endpoint FastAPI.
generate-command
Génération Commande Symfony.