enferno AGENTS.md

Repository instructions for Enferno, a web framework built with Flask on the server and Vue on the browser, with database, authentication, and background-job components.

In plain words
What is it for?
Use them when working on routes, models, templates, authentication, background tasks, configuration, or application setup.
Why use it?
They explain the framework’s architecture and file layout so changes go in the correct place and follow the project’s conventions.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/level09/enferno/agents-md
Clone the repo
git clone --depth 1 https://github.com/level09/enferno

Made for: Codex, OpenCode.

Per session 6,870 This file is loaded in full into every session.
When invoked 6,870 The same file — it is already loaded in full.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.06870 $0.06870
Opus 5 $0.03435 $0.03435
Sonnet 5 $0.01374 $0.01374
Haiku 4.5 $0.00687 $0.00687

Measured 2d ago against content hash 04956000f917, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

enferno AGENTS.md scanned grade C with 2 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 2d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

&& rm -rf /var/lib/apt/lists/*

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

axios.post('/api/endpoint', data, {
AGENTS.md · 1,128 lines

How it starts

The opening of the file, as written. The whole thing — 1,128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This file provides comprehensive architectural patterns and coding standards for AI agents working with the Enferno framework.

Framework Overview

Enferno is a Flask-based web framework optimized for rapid development with modern tooling:

  • Backend: Flask 3.x with Blueprint organization
  • Frontend: Vue 3 + Vuetify (no build step required)
  • Database: SQLAlchemy 2.x with modern statement-based queries
  • Auth: Flask-Security-Too with 2FA, WebAuthn, OAuth support
  • Tasks: Celery + Redis for background processing
  • Package Manager: uv for fast dependency management

Project Structure

enferno/
├── enferno/                # Main application package
│   ├── app.py             # Application factory (create_app)
│   ├── settings.py        # Environment-based configuration
│   ├── extensions.py      # Flask extensions initialization
│   ├── commands.py        # Custom Flask CLI commands
│   ├── public/            # Public routes (no auth)
│   │   ├── views.py
│   │   ├── models.py
│   │   └── templates/
│   ├── user/              # Authentication & user management
│   │   ├── views.py
│   │   ├── models.py
│   │   ├── forms.py
│   │   └── templates/
│   ├── portal/            # Protected dashboard/admin
│   │   ├── views.py
│   │   └── templates/
│   ├── services/          # Business logic layer
│   ├── tasks/             # Celery task definitions
│   ├── utils/             # Utility functions
│   ├── static/            # CSS, JS, images
│   │   ├── css/
│   │   ├── js/
│   │   └── img/
│   └── templates/         # Global Jinja2 templates
├── docs/                  # Documentation
├── nginx/                 # Nginx configuration
├── instance/              # Instance-specific files (gitignored)
├── pyproject.toml         # Dependencies and project metadata
├── uv.lock               # Lock file for reproducible installs
├── .env                   # Environment variables (gitignored)
├── .env-sample            # Environment template
├── setup.sh              # Setup script
├── run.py                # Application entry point
├── Dockerfile            # Docker configuration
└── docker-compose.yml    # Docker Compose orchestration

Read the full file on GitHub · 1,128 lines

Changes

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.

  1. 2d ago First seen · 1,128 lines · 6,870 tokens per session scan C 04956000f917

Subscribe to this mod's changes

enferno AGENTS.md is an instructions file published in the GitHub repository level09/enferno (569 stars, last pushed 6d ago), licensed MIT. It adds 6,870 tokens to every session, about $0.0343 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.