Borrowing it
Nothing to install: this file belongs to toyamarinyon/giselle. 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/toyamarinyon/giselle/main/AGENTS.mdgit clone --depth 1 https://github.com/toyamarinyon/giselleWrote 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/toyamarinyon/giselle/agents-md)<a href="https://agentmods.dev/instructions/toyamarinyon/giselle/agents-md"><img src="https://agentmods.dev/badge/instructions/toyamarinyon/giselle/agents-md.svg" alt="Measured on agentmods" 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.03417 | $0.03417 |
| Opus 5 | $0.01708 | $0.01708 |
| Sonnet 5 | $0.00683 | $0.00683 |
| Haiku 4.5 | $0.00342 | $0.00342 |
Grade A, and why
giselle 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 7d 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.
This is a copy
100% identical to giselle AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Giselle Development Guide
Development Philosophy
Core Principle: Less is more
Keep every implementation as small and obvious as possible.
Guidelines
- Simplicity first – Prefer the simplest data structures and APIs that work
- Avoid needless abstractions – Refactor only when duplication hurts
- Remove dead code early –
pnpm tidyscans for unused files/deps and lets you delete them in one command - Minimize dependencies – Before adding a dependency, ask "Can we do this with what we already have?"
- Consistency wins – Follow existing naming and file-layout patterns; if you must diverge, document why
- Explicit over implicit – Favor clear, descriptive names and type annotations over clever tricks
- Fail fast – Validate inputs, throw early, and surface actionable errors
- Let the code speak – If you need a multi-paragraph comment, refactor until intent is obvious
Project Overview
Giselle is built to design and run AI workflows beyond prompt chains. Not a chat. Not a chain. A system you can run.
Key Features:
- Visual editor
- Instant execution
- No infra headaches
- Open source — self-host or use our cloud
Architecture
Monorepo Structure
Giselle uses a Turborepo monorepo with pnpm workspaces, organized into four main directories:
/workspace
├── apps/ # Deployable applications
│ ├── studio.giselles.ai/ # Giselle Cloud (production)
│ └── ui.giselles.ai/ # UI component showcase
├── packages/ # Published SDK packages (@giselles-ai/*)
├── internal-packages/ # Internal shared packages (@giselle-internal/*)
└── tools/ # Development utilities
Package Layers
SDK Packages (packages/@giselles-ai/*):
protocol— Core domain types and schemas (Workspace, Node, Task, Generation)giselle— Engine implementation (tasks, generations, triggers, integrations)react— React hooks and components for client integrationnextjs— Next.js integration with route handlerslanguage-model— Language model abstractions and cost calculationslanguage-model-registry— Provider-specific model implementationsrag— RAG pipeline (chunking, embedding, querying)github-tool— GitHub integration utilities
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.
- 7d ago First seen · 455 lines · 3,417 tokens per session scan A 2014a82fb07c
giselle AGENTS.md is an instructions file published in the GitHub repository toyamarinyon/giselle (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 3,417 tokens to every session, about $0.0171 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to giselle AGENTS.md, differing in 0 lines, and is treated as a copy.
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.
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.
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 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
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.