Borrowing it
Nothing to install: this file belongs to jiahuiqu17/paper-signal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jiahuiqu17/paper-signal/main/AGENTS.mdgit clone --depth 1 https://github.com/jiahuiqu17/paper-signalWrote 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/jiahuiqu17/paper-signal/agents-md)<a href="https://agentmods.dev/instructions/jiahuiqu17/paper-signal/agents-md"><img src="https://agentmods.dev/badge/instructions/jiahuiqu17/paper-signal/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.
<a href="https://agentmods.dev/instructions/jiahuiqu17/paper-signal/agents-md"><img src="https://agentmods.dev/badge/instructions/jiahuiqu17/paper-signal/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00508 | $0.00508 |
| Opus 5 | $0.00254 | $0.00254 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
paper-signal 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paper Signal contributor instructions
Treat skills as behaviour-shaping code and generated images as test artifacts. Start from a repeatable user problem, preserve the project's narrow visual thesis, and keep every claim about quality inspectable.
Before editing
- For documentation-only corrections, compatibility reports, or shared community examples, follow
.github/CONTRIBUTING.mdand runmake checkwhen editing the repository; architecture reading is not required. - Read
docs/architecture.mdbefore changing routes, shared visual rules, or skill boundaries. - Read
docs/evaluation.mdbefore changing prompts, preservation rules, or generated examples. - Run
make checkbefore and after the change. Runmake integrationwhen schemas, packaging, installation, or metadata changes. - Keep one conceptual change per branch or pull request.
Repository boundaries
- Keep each
SKILL.mdconcise, imperative, under 500 lines, and limited tonameanddescriptionfrontmatter. - Put reusable depth in one-level
references/, deterministic operations inscripts/, and output templates inassets/. - Keep
paper-signalas the router; do not duplicate shared rules across specialist skills. - Add a decision rule, contract, test, or transferable example. Do not expand the system with style adjectives alone.
- Preserve the zero-dependency runtime. Development-only validation dependencies belong in
requirements-dev.txt.
Visual and evidence changes
- Keep the exact prompt, manifest, selected bitmap,
qa.md, andASSETS.mdfor every committed visual example. - Inspect changed outputs at original size and phone-thumbnail size. Subject or text integrity failures block acceptance.
- Use fictional, licensed, or clearly redistributable inputs. Never commit private paths, credentials, student records, or unlicensed reference assets.
- Do not claim a prompt was rendered or visually checked without the real bitmap and an observation-based QA record.
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 · 34 lines · 508 tokens per session scan A eff244c88ad0
paper-signal AGENTS.md is an instructions file published in the GitHub repository jiahuiqu17/paper-signal (109 stars, last pushed 29d ago), licensed MIT. It adds 508 tokens to every session, about $0.0025 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
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 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.
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.