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/hosamzewain/ai-assisted-development-framework/agents-mdgit clone --depth 1 https://github.com/HosamZewain/ai-assisted-development-frameworkWrote 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/hosamzewain/ai-assisted-development-framework/agents-md)<a href="https://agentmods.dev/instructions/hosamzewain/ai-assisted-development-framework/agents-md"><img src="https://agentmods.dev/badge/instructions/hosamzewain/ai-assisted-development-framework/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.00454 | $0.00454 |
| Opus 5 | $0.00227 | $0.00227 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
ai-assisted-development-framework 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 6d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project AI Instructions
This repository uses a repo-based AI Development Framework.
AI tools must keep changes safe, minimal, and consistent with the existing codebase.
Default Reading
Before any code change, read:
docs/ai/context.md
Do not read all AI docs by default.
Read extra docs only when relevant:
- Architecture / modules / data flow / deployment →
docs/ai/architecture.md - Behavior changes / validation / tests →
docs/ai/testing-policy.md - Auth / permissions / tenant data / logs / PII / admin / integrations →
docs/ai/security-policy.md - Release / production-impacting changes →
docs/ai/release-policy.md - Code review tasks →
docs/ai/code-review.md - Unclear domain terms →
docs/ai/glossary.md
Skills
Use only the relevant skill:
- Backend change →
.agents/skills/backend-change/SKILL.md - Frontend change →
.agents/skills/frontend-change/SKILL.md - Bug fix →
.agents/skills/bug-fix/SKILL.md - Code review →
.agents/skills/code-review/SKILL.md - Release check →
.agents/skills/release-check/SKILL.md
Work Rules
- Do not perform a full codebase scan unless explicitly required.
- Inspect only impacted modules and nearby related files.
- Make the smallest safe change.
- Follow existing patterns.
- Do not perform broad refactors unless explicitly requested.
- Do not remove existing behavior unless explicitly requested.
- Do not hardcode customer-specific, tenant-specific, or environment-specific behavior.
- Do not bypass permissions, audit logs, or security checks.
- Do not expose secrets, tokens, credentials, or sensitive data.
- Do not change database schema without migration and rollback notes.
Testing
When behavior changes:
- Add or update relevant tests when possible.
- Run the smallest relevant test set.
- Run lint/typecheck if available and relevant.
- If tests cannot be run, clearly say why.
Final Response
Always include:
- Changed files
- What changed
- Tests run
- Tests not run, if any
- Risks
- Rollback notes
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.
- 6d ago First seen · 66 lines · 454 tokens per session scan A 59e38951d9ce
ai-assisted-development-framework AGENTS.md is an instructions file published in the GitHub repository HosamZewain/ai-assisted-development-framework (55 stars, last pushed 3mo ago), licensed MIT. It adds 454 tokens to every session, about $0.0023 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
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).
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.
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.
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 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).
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.