What is 2dph AGENTS.md?

Repository instructions for 2dph, an eSlider project that treats documented evidence as the basis for decisions and development work.

Use them when reading project plans, changing code or documentation, managing issues and pull requests, or synchronizing the Gitea repository with its GitHub mirror.

They identify which documents are authoritative and set rules for using Gitea as the main code-hosting service, reducing the risk of following stale plans or publishing private project material.

2dph AGENTS.md — Instructions file by eSlider

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/eslider/2dph/agents-md

Clone the repo

git clone --depth 1 https://github.com/eSlider/2dph

Made for: Codex, OpenCode.

Per session 3,756 This file is loaded in full into every session.

When invoked 3,756 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.

Model	Per session	Once invoked
Fable 5	$0.03756	$0.03756
Opus 5	$0.01878	$0.01878
Sonnet 5	$0.00751	$0.00751
Haiku 4.5	$0.00376	$0.00376

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

Security

Grade A, and why

2dph 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 · 245 lines

How it starts

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

AGENTS.md — 2dph (deductionphile)

Evidence-first brain over the ops/eSlider stack. Facts need proof or they are (not confirmed).

Read first: PLAN → docs → roadmap. Standards epic: #88.

Work — Gitea only (MUST)

Canonical home: git.produktor.io/eSlider/2dph. All github.com/eSlider/go-* libraries are owned; their working home is Gitea git.produktor.io/eSlider/<repo> ([#101]). GitHub is a publish mirror only. Issues, PRs, reviews, epics, milestones, releases exist only on Gitea — never on GitHub.
GitHub = showroom (rule #190): nothing non-project lands on the GitHub mirror — no sales/offer material, no internal paths/hosts/ports, no host-specific docs. Before pushing a branch/tag to GitHub, verify the diff is project content (like the #142 gitleaks scan, but by content too). A leaked feature is purged from GitHub history with git filter-repo (precedent #152/#190); Gitea stays the canonical home.
Git transport (current truth, #81/#73): git ops are HTTPS + token only — the Gitea SSH deploy-key (:222) is broken on write (#73 closed as obsoleted by this). Issues/PRs via the tea CLI (API base https://git.produktor.io, token in ~/.tea/tea.yml). Some local checkouts still point origin at the SSH :222 key, which is broken on write — reset origin to the HTTPS+token URL or push via tea. Never embed a token in a remote URL — credentials live in ~/.tea/tea.yml / credential helpers.
Every task starts as a Gitea issue на русском. Epics group child issues; milestones are sprints. Agents report progress as issue comments like senior engineers and close issues via commit refs ((#id)).
Roles: PO owns priorities, acceptance and dispatch; SE sub-agents implement TDD-style against one issue each; sync happens through Gitea only.
Branches type/slug#<issue>; Conventional Commits type(scope): summary (#id) (feat|fix|refactor|chore|docs|test). PR → review → CI green → merge into main (single line, #213). No direct pushes to main.
SemVer tags on Gitea after merge: fix:→PATCH, feat:→MINOR, breaking (!)→MAJOR; next version computed by the semver tool.

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

2d ago First seen · 245 lines · 3,756 tokens per session scan A 7519b44f5ca2

Subscribe to this mod's changes

2dph AGENTS.md is an instructions file published in the GitHub repository eSlider/2dph (2 stars, last pushed 3d ago), licensed MIT. It adds 3,756 tokens to every session, about $0.0188 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.

deduction fulltext hybrid-search knowledge-graph mcp model2vec

2dph AGENTS.md

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

AGENTS.md — 2dph (deductionphile)

Work — Gitea only (MUST)

What this file has done since we first saw it

Other instructions, from other repositories

Muninn GEMINI.md

fortemi CLAUDE.md

fortemi AGENTS.md

book-brain AGENTS.md

mcp-skillset CLAUDE.md

m_flow AGENTS.md