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/sitcon-tw/credits-profiles/agents-mdgit clone --depth 1 https://github.com/sitcon-tw/credits-profilesWrote 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/sitcon-tw/credits-profiles/agents-md)<a href="https://agentmods.dev/instructions/sitcon-tw/credits-profiles/agents-md"><img src="https://agentmods.dev/badge/instructions/sitcon-tw/credits-profiles/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.02162 | $0.02162 |
| Opus 5 | $0.01081 | $0.01081 |
| Sonnet 5 | $0.00432 | $0.00432 |
| Haiku 4.5 | $0.00216 | $0.00216 |
Grade A, and why
credits-profiles 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository maintains opt-in public profile files for SITCON Credits contributors and display-only site profiles derived from public SITCON event websites.
The public reader-facing documentation should be written in Traditional Chinese for Taiwan unless a file explicitly targets another audience. This file is written in English because it is intended for LLM agents and automated maintainers.
Instruction Source of Truth
AGENTS.md is the single maintained instruction source for coding agents in this repository. Do not copy these rules into tool-specific instruction files.
Compatibility entrypoints may exist only as thin pointers to AGENTS.md. For example, CLAUDE.md imports AGENTS.md for Claude Code. If a tool does not automatically load AGENTS.md, load this file manually before editing.
Repository Role
- This repository stores low-risk, opt-in profile data for GitHub usernames.
- This repository also stores maintainer-controlled site profile data under
site-profiles/. - The main SITCON Credits repository is https://github.com/sitcon-tw/credits.
- Historical event appearances, event scope, role records, source URLs, and accepted identity links are not maintained here.
- A profile file existing here does not prove that any historical appearance belongs to that GitHub username.
- A site profile existing here does not prove contributor opt-in or identity merge approval.
Data Boundary
Profile files live at profiles/<github_username>.json. The filename is the profile link key. Do not add a separate identity identifier, alias list, appearance list, source URL list, or historical contribution list inside profile files.
Allowed profile fields are documented by profiles/README.md, profiles/_template.json, and schemas/profile.schema.json. The current low-risk fields are:
- preferred public display name
- biography
- avatar URL
- public email address
- public links
Do not expand the schema unless the user explicitly asks for a profile policy or schema change.
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.
- 5d ago First seen · 127 lines · 2,162 tokens per session scan A 57f43957a210
credits-profiles AGENTS.md is an instructions file published in the GitHub repository sitcon-tw/credits-profiles (2 stars, last pushed 9d ago), licensed MIT. It adds 2,162 tokens to every session, about $0.0108 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.
Other instructions, from other repositories
vercel-action CLAUDE.md
Instructions for amondnet/vercel-action, covering claude.md, project overview, package manager, essential commands and development.
setup-chromedriver CLAUDE.md
Claude Code instructions for nanasess/setup-chromedriver, covering claude.md, commands, build and development, running a single test and or.
databricks-template CLAUDE.md
Instructions for andre-salvati/databricks-template, covering claude.md, project overview, tooling: mcp servers, cli, skills → see specs/tooling.md, commands and architecture & data model → see specs/.
ConsultMe CLAUDE.md
Claude Code instructions for Tarek-Bohdima/ConsultMe, covering claude.md, project context, common commands, module graph and conventions enforced by tooling.
omen CLAUDE.md
Claude Code instructions for panbanda/omen, covering claude.md, build and development commands, setup git hooks (run once after clone), format code and run linter.
ai-research-arm CLAUDE.md
Claude Code instructions for guzus/ai-research-arm, covering claude.md, project overview, core pipeline architecture, key components and scripts (scripts/).