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 agentmods add instructions/n-side-dev/wefa/agents-mdgit clone --depth 1 https://github.com/n-side-dev/wefaWhat 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 | $0.01037 | $0.01037 |
| Opus 5 | $0.00518 | $0.00518 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
wefa AGENTS.md 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 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.
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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
N-SIDE WeFa - Agent Guide
Product
WeFa (Web Factory) is N-SIDE's internal toolkit for assembling full-stack product experiences quickly. The monorepo ships three artifacts on one shared version:
django/publishes thenside-wefaDjango toolkit.vue/publishes the@nside/wefaVue 3 component library.bff/publishes the Flask backend-for-frontend used for OAuth/session/cookie flows and backend proxying.
Purpose
This file provides durable repository-wide guidance. Keep shared rules here, keep workspace-specific rules in nested AGENTS.md files, and keep reusable task workflows in .agents/skills/.
Codex loads AGENTS instructions from the repository root down to the current working directory. Later files are more specific.
Repository Map
README.mdis the top-level overview; defer to per-workspaceREADME.mdfiles for package specifics.django/contains reusable Django apps plus thedemo/validation project. See django/AGENTS.md.vue/contains the library, demo app, Storybook docs, and package tooling. See vue/AGENTS.md.bff/contains the Flask BFF and its generated OpenAPI spec. See bff/AGENTS.md..agents/skills/contains repo-local Codex skills.docs/agent-roadmap.mdrecords cross-cutting infrastructure direction.code_review.mdis the review checklist.PLANS.mdis the plan template for larger multi-step work.
Instruction Routing
- For Vue work in consuming projects that use
@nside/wefa, usewefa-vue-cookbook. - For frontend work inside this repository's
vue/workspace, loadwefa-vue-cookbookfirst and thenwefa-vue-frontend. wefa-vue-cookbookis the shared base skill: it applies both to consuming apps and to shared Vue conventions inside this repo.wefa-vue-frontendadds only repo-specific maintainer guidance for this monorepo'svue/workspace: exports, docs, demo wiring, generated artifacts, tests, and quality-gate expectations.- For TanStack Query work in
vue/, also usewefa-tanstack-querywhen the task is specifically about query wiring, invalidation, mutation flows, or wrapper choice. - For
django/work, follow django/AGENTS.md. - For
bff/work, follow bff/AGENTS.md. - For cross-cutting changes, coordinate backend/API shape first, then update consumers and documentation in the affected workspaces.
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.
- 2d ago First seen · 70 lines · 1,037 tokens per session scan A f562ed90d94e
wefa AGENTS.md is an instructions file published in the GitHub repository n-side-dev/wefa (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 1,037 tokens to every session, about $0.0052 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.