agent-profile AGENTS.md

A project instruction file for agent-profile, a TypeScript project that configures local AI-agent tools. It defines which development practices, permissions, safety rules, and project boundaries agents must follow.

In plain words
What is it for?
Use it to guide agent work in the project, including required specification and test practices, allowed operations, forbidden data handling, supported clients, and the final completion checks.
Why use it?
Agents need clear project-specific rules for reading files, changing code, testing, handling secrets, and using external services. This file makes those expectations explicit.

Instructions file for CodexOpenCode

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 instructions/jsuvic/agent-profile/agents-md
Clone the repo
git clone --depth 1 https://github.com/jsuvic/agent-profile

Made for: Codex, OpenCode.

Per session 939 This file is loaded in full into every session.
When invoked 939 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00939 $0.00939
Opus 5 $0.00469 $0.00469
Sonnet 5 $0.00188 $0.00188
Haiku 4.5 $0.00094 $0.00094

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

Security

Grade A, and why

agent-profile 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 2d 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.

AGENTS.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Instruction Precedence

If generated and manual instructions conflict, follow the manual project instructions unless they would weaken safety, privacy, or permission limits. Safety, privacy, and explicit deny rules always win.

Project

Name: agent-profile

Description: Local AI-agent setup.

Stack

  • Languages: typescript
  • Frameworks: None declared
  • Package managers: npm
  • Testing: None declared

Enabled AI Clients

  • Codex
  • Claude

Development Workflow

  • SDD: Required
  • TDD: Required
  • Final implementation review: Required

Permissions

Permission Mode
filesystem read allow
filesystem write ask
shell run ask
dependency install ask
external network ask
secrets access deny
production access deny

Safety Rules

  • No source-code upload.
  • No secret upload.
  • No literal tokens in generated configs.
  • No telemetry by default.
  • No hosted execution in the MVP.

Scope Limits

Cursor, Aider, Copilot, hosted gateways, enterprise RBAC, SIEM integrations, and custom sandbox runtimes are out of scope unless an approved spec adds them.

Completion Checklist

  • Run tests.
  • Run golden tests when generated files change.
  • Run doctor/check once available.
  • Review the implementation against the relevant spec.
  • List remaining risks or TODOs.

AGENTS.md

Project

This repository implements a local-first AI Agent Profile Compiler.

The tool defines one canonical ai-profile.yaml and compiles it into agent-specific configuration for Tabnine, Codex, and Claude.

Product Principles

  • Local-first by default.
  • No source-code upload.
  • No secret upload.
  • No hosted execution in the MVP.
  • Generated files must be deterministic.
  • Safety checks are part of the product, not an afterthought.
  • Prefer explicit contracts over implicit behavior.

Read the full file on GitHub · 167 lines

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. 2d ago First seen · 167 lines · 939 tokens per session scan A b593ed9fd904

Subscribe to this mod's changes

agent-profile AGENTS.md is an instructions file published in the GitHub repository jsuvic/agent-profile (3 stars, last pushed 9d ago), licensed Apache-2.0. It adds 939 tokens to every session, about $0.0047 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-31.