Frailen, set up by your agent.
Your coding agent can read the whole site, write the tool cards from your OpenAPI and prepare the integration on a branch. You review and approve; it never publishes.
Set up Frailen for me. Fetch https://frailen.com/get-started.md and follow it.One line for Claude Code, Cursor or Codex. Your agent reads get-started.md and follows it step by step.
claude "Set up Frailen for me. Fetch https://frailen.com/get-started.md and follow it."In Claude Code, from your terminal.
Or the whole prompt
What the playbook does, in a single prompt, if you'd rather see all of it before pasting it.
Read https://frailen.com/llms.txt and https://frailen.com/desarrolladores.md. Then set up Frailen in this repository, on a new branch: 1. Find our OpenAPI spec, or the API routes a support agent may touch. Write one Frailen tool card per operation in herramientas/*.yaml, with its pattern, damage flags (dinero, masivo, terceros, sin_reversa), how it's undone and how it's read back. Only a GET can be a read. 2. Add POST /frailen/token to our backend: it exchanges our signed session (an ES256 JWT) for an API token for that same user, valid for 300 seconds or less (RFC 8693). 3. Add the Frailen chat tag to our app's main layout. 4. Write three test bench cases in pruebas/ for our most common support requests. Don't approve, publish or deploy anything. Finish with a summary of what you did and what needs a human decision.
Paste it into Claude Code, Cursor, Codex or any agent that can read a URL.
A prompt for each step
If you'd rather go step by step, or just want your agent to evaluate it before touching anything.
Read https://frailen.com/llms-full.txt. Then look at our codebase and tell me whether Frailen fits our product: which API operations would become tools, which would carry damage, what we'd still need to build and what you'd ask in the demo. Don't change anything.
Read https://frailen.com/desarrolladores.md. From our OpenAPI spec, write Frailen tool cards in herramientas/, one per operation our support agent should use. Only a GET can be a read. Give every write its damage flags (dinero, masivo, terceros, sin_reversa), se_deshace_con if it can be undone, and relee_con with the GET that proves it held. List the operations you left out and why.
Read https://frailen.com/desarrolladores.md. Add POST /frailen/token to our backend (RFC 8693 token exchange): it receives our signed session as subject_token (an ES256 JWT), verifies it against our JWKS, and returns a Bearer token for that same user that expires in 300 seconds or less. Add tests. Never log the session or the token.
Read https://frailen.com/desarrolladores.md. Add the Frailen chat to our app: the tag in the main layout, with data-empresa and data-asercion pointing to a backend route that signs a 60-second ES256 assertion for the signed-in user. Pass the current page and the open object as context.
Read https://frailen.com/desarrolladores.md. Write five Frailen test bench cases in pruebas/ for the requests our support team gets most. Each case has the user's message, the expected final state read back through a GET tool, and a rule written before it runs. One case must check that something else did not change.
Read https://frailen.com/seguridad.md and https://frailen.com/llms.txt. Review Frailen's security model against our product: identity and tokens, what's stored and for how long, isolation between companies, and how the brake works. List the questions our security team should ask before a pilot, and what Frailen says it doesn't have yet.
Read https://frailen.com/precios.md. Our product handles about [conversations per month] support conversations a month. Estimate which Frailen tier fits, what we'd pay with those reference prices, and what spending cap you'd set. Say which numbers are assumptions.
What your agent can read
The whole site, with no JavaScript and no guessing.
- Frailen's summary for agents, with links to everything else.
- Every page in a single file, to load it in one go.
Every page in Markdown
Add.mdto the path:https://frailen.com/precios.md. The home page ishttps://frailen.com/index.md.In both languages
English at the root; Spanish under/es(https://frailen.com/es/llms.txt).
Rules for your agent
Add them to your repository's AGENTS.md or CLAUDE.md. They say what the agent prepares and what it never does.
## Frailen - Before touching Frailen files, read https://frailen.com/llms.txt (and https://frailen.com/llms-full.txt if you need the detail). - Tool cards live in herramientas/*.yaml and test bench cases in pruebas/*.yaml. - Only a GET can be a read. Every write carries its damage flags; never remove one to make a test pass. - Never log or commit sessions, tokens or keys. - You prepare the integration on a branch. A person approves the tools and turns the agent on with their passkey: you never approve, publish or deploy.
SoonThe CLI (@frailen/cli) and an MCP server for coding agents are being built. Until then, your agent works from these files and these prompts.