developer-guidelines.fa

A Persian-language guide to building with Fabric. It explains how to work with Fabric without struggling against its protocol, the rules systems use to communicate.

In plain words
What is it for?
Use it as a practical reference while building agents or other work that uses Fabric.
Why use it?
It helps developers and agents avoid common misunderstandings when creating things for Fabric.

Agent

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 agents/fabric-protocol/fabric/developer-guidelines.fa
Clone the repo
git clone --depth 1 https://github.com/Fabric-Protocol/fabric
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 654 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin unknown 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.00000 $0.00654
Opus 5 $0.00000 $0.00327
Sonnet 5 $0.00000 $0.00131
Haiku 4.5 $0.00000 $0.00065

Measured yesterday against content hash da5e1a0c839c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

developer-guidelines.fa scanned grade C with 1 finding 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 yesterday.

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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

# راهنمای توسعه‌دهندگان Fabric این راهنما توضیح می‌دهد چگونه با Fabric کار بسازید بدون اینکه با خود پروتکل بجنگید. ## سیستم را همان‌طور که طراحی شده استفاده کنید - موجودی را رایگان منتشر کنید - کشف را متری و دارای هزینه
docs/agents/developer-guidelines.fa.md · 69 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 69 lines · 0 tokens per session scan C da5e1a0c839c

Subscribe to this mod's changes

developer-guidelines.fa is an agent published in the GitHub repository Fabric-Protocol/fabric (1 stars, last pushed 4mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 654 tokens. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other agents, from other repositories

business-analyst

Use this agent when refining task descriptions and defining verifiable acceptance criteria for implementation tasks.

NeoLabHQ/context-engineering-kit · 22 tokens

code-reviewer

Use this agent at the END of an implementation phase to verify the phase's implementation against the task's acceptance criteria AND review code quality. Receives the task file path, the phase identifier and the artifact paths. Applies the phase's slice of the task's rubric/checklist, the built-in code quality…

NeoLabHQ/context-engineering-kit · 79 tokens

developer

Use this agent when implementing a single step of a task. Receives the task file path AND that step's sub-task file path. Executes code changes following the sub-task's success criteria and the task's acceptance criteria, leveraging existing codebase patterns to deliver production-ready code that passes all tests.

NeoLabHQ/context-engineering-kit · 61 tokens

tech-lead

Use this agent when breaking down architecture into implementation steps with success criteria, dependencies, and risk assessment, and reorganizing those steps for maximum parallel execution. Transforms architectural blueprints into executable, parallelized task sequences written as per-step sub-task files grouped…

NeoLabHQ/context-engineering-kit · 60 tokens

tech-writer

Creates and maintains comprehensive, accessible technical documentation by transforming complex concepts into clear, structured content that helps users accomplish their tasks.

NeoLabHQ/context-engineering-kit · 27 tokens

judge

Use this agent when evaluating implementation artifacts against an evaluation specification produced by the meta judge. Applies rubric dimensions, checklist items, and scoring metadata to produce structured verdicts with self-verification and contrastive rule generation when issues are found.

NeoLabHQ/context-engineering-kit · 48 tokens