Fulling is an AI-powered full-stack engineering workspace project whose current foundation provides sign-in, persistent user and session data, protected application access, and a user-scoped boundary for Kubernetes credentials. It is intended for dedicated AI workspaces that combine skills, files, memory, scripts, and runtime environments; the catalogue entry supplies an instruction for working with it.
Borrowing it
Nothing to install: this file belongs to FullAgent/fulling. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/FullAgent/fulling/main/AGENTS.mdgit clone --depth 1 https://github.com/FullAgent/fullingWrote 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/instructions/fullagent/fulling/agents-md)<a href="https://agentmods.dev/instructions/fullagent/fulling/agents-md"><img src="https://agentmods.dev/badge/instructions/fullagent/fulling/agents-md/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/instructions/fullagent/fulling/agents-md"><img src="https://agentmods.dev/badge/instructions/fullagent/fulling/agents-md.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.00874 | $0.00874 |
| Opus 5.5 | $0.00350 | $0.00350 |
| Sonnet 5.5 | $0.00175 | $0.00175 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
fulling 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 1mo 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI agents when working with code in this repository.
Project Overview
Fulling v3.0 is building dedicated AI workspaces — persistent, personalizable environments with skills, files, memory, scripts, and runtime. Think of it as an out-of-the-box AI toolkit that users can customize and share.
Read docs/architecture.md before product or architecture work. It is the source of truth for the v3 workspace model.
Tech Stack
- Next.js 16 (App Router) + React 19 + TypeScript
- Tailwind CSS v4 + Shadcn/UI
- Node.js 24 + Prisma + Better Auth
- Kubernetes + PostgreSQL
Code Conventions
- TypeScript strict mode
- Functional components with hooks
- In
lib/platform/: one primary action per file, noun directories + verb file names, boundary comment above main exported function - Route-specific components in
_components/directory - Shared components in top-level
components/
Current Implementation Context
- GitHub is the only authentication provider.
- Better Auth stores users, provider accounts, and sessions in PostgreSQL.
- Each user may store one plaintext kubeconfig; browser APIs never return it.
- Always use the user-specific K8s service:
const k8sService = await getK8sServiceForUser(userId). - The current user-level kubeconfig is a foundation boundary, not the final v3 Workspace Runtime ownership model.
UI Direction
The active v3 design system is defined in docs/design.md. It derives from SST and is the source of truth for Fulling's visual language, tokens, typography, spacing, components, states, and responsive behavior. Read it before substantial UI work. Existing UI that conflicts with it is migration work, not design precedent.
Avoid generic AI copywriting cliches such as "Elevate", "Seamless", and "Unleash".
Key Files
- docs/architecture.md — v3 system architecture and product model
- docs/design.md — active v3 design system and SST-derived style reference
lib/auth/— Better Auth and application session boundarylib/kubeconfig/— User credential persistencelib/k8s/— Validation and user-specific Kubernetes service
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.
- 1mo ago First seen · 105 lines · 874 tokens per session scan A 4e446afeb2f3
fulling AGENTS.md is an instructions file published in the GitHub repository FullAgent/fulling (2,444 stars, last pushed 2mo ago), licensed MIT. It adds 874 tokens to every session, about $0.0035 per session on Opus 5.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
vscode buildNext.instructions.md
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
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, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.