What is AwesomeSalesforceSkills AGENTS.md?

Repository instructions for maintaining agents in AwesomeSalesforceSkills, a collection of reusable Salesforce guidance. They explain where agents live, which shared rules to read, and which checks to run after changes.

Use them when adding or editing agent files, searching existing knowledge, reusing shared probes, and running agent or repository validation.

They give contributors a consistent process for changing agents without skipping required rules, formats, or validation.

How BanibrataChatterjee/AwesomeSalesforceSkills configures Codex and O

Reuse

Borrowing it

Nothing to install: this file belongs to BanibrataChatterjee/AwesomeSalesforceSkills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/BanibrataChatterjee/AwesomeSalesforceSkills/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkills

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/banibratachatterjee/awesomesalesforceskills/agents-md/github.svg)](https://agentmods.dev/instructions/banibratachatterjee/awesomesalesforceskills/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/banibratachatterjee/awesomesalesforceskills/agents-md"><img src="https://agentmods.dev/badge/instructions/banibratachatterjee/awesomesalesforceskills/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/banibratachatterjee/awesomesalesforceskills/agents-md"><img src="https://agentmods.dev/badge/instructions/banibratachatterjee/awesomesalesforceskills/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 523 This file is loaded in full into every session.

When invoked 523 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00523	$0.00523
Opus 5	$0.00262	$0.00262
Sonnet 5	$0.00105	$0.00105
Haiku 4.5	$0.00052	$0.00052

Measured 10d ago against content hash 3260572781fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

AwesomeSalesforceSkills 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 10d 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 · 56 lines

How it starts

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

AGENTS.md

Repo-local agent instructions live in AGENT_RULES.md.

Any coding agent working in this repository must:

Read AGENT_RULES.md before creating or materially revising a skill.
Treat SKILL.md frontmatter as the canonical skill metadata source.
Use python3 scripts/search_knowledge.py before creating a new skill or claiming a coverage gap.
Run python3 scripts/skill_sync.py and python3 scripts/validate_repo.py after skill changes.
Never hand-edit generated files in registry/, vector_index/, or docs/SKILLS.md.

Working on agents (not skills)

Agents live under agents/<slug>/AGENT.md. Before editing or adding one:

Read agents/_shared/AGENT_CONTRACT.md for the frontmatter spec, required section order, confidence rubric, and structured citation/output formats.
For skill-builder agents, also read agents/_shared/SKILL_BUILDER_CORE.md.
Reuse probes from agents/_shared/probes/ instead of hand-rolling MCP queries.
Use refusal codes from agents/_shared/REFUSAL_CODES.md in output envelopes.

After editing any AGENT.md run:

python3 scripts/validate_repo.py --agents

validate_repo.py --all runs both skill and agent validation (slow; skill compilation + query fixtures). Use --agents or --skills-only for fast iteration.

Reading / updating the skill queue

MASTER_QUEUE.md is the authoritative queue. Do not grep/sed it — use:

python3 scripts/queue_reader.py --summary
python3 scripts/queue_reader.py --next --status TODO,RESEARCHED
python3 scripts/queue_reader.py --set-status IN_PROGRESS \
  --id <skill-name-or-row-id> --actor "<agent-name>@<host>"

See docs/QUEUE_FORMAT_PROPOSAL.md for the reader contract and the deferred YAML migration plan.

Running agent evals

python3 evals/agents/scripts/run_agent_evals.py --structure   # lint fixtures
python3 evals/agents/scripts/run_agent_evals.py --agent field-impact-analyzer --output path/to/output.json

Read the full file on GitHub · 56 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.

10d ago First seen · 56 lines · 523 tokens per session scan A 3260572781fe

Subscribe to this mod's changes

AwesomeSalesforceSkills AGENTS.md is an instructions file published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 523 tokens to every session, about $0.0026 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.

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

AwesomeSalesforceSkills: Instructions file for Codex