Borrowing it
Nothing to install: this file belongs to john-ops-lab/EasySourceFlow. 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/john-ops-lab/EasySourceFlow/main/AGENTS.mdgit clone --depth 1 https://github.com/john-ops-lab/EasySourceFlowWrote 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/john-ops-lab/easysourceflow/agents-md)<a href="https://agentmods.dev/instructions/john-ops-lab/easysourceflow/agents-md"><img src="https://agentmods.dev/badge/instructions/john-ops-lab/easysourceflow/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.00827 | $0.00827 |
| Opus 5 | $0.00413 | $0.00413 |
| Sonnet 5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
EasySourceFlow 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 6d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
EasySourceFlow is a Python 3.10+ local content summarization service with HTTP, Web UI, and MCP entry points.
src/easysourceflow_core/: core daemon, HTTP API, Web UI, extractors, digest generation, SQLite store, output writing, backup, cleanup, and maintenance logic.src/easysourceflow_core/extractors/: source-specific extraction for web pages, WeChat articles, and video platforms.src/easysourceflow_mcp/: stdio MCP adapter used by agents.tests/:unittestcoverage for core behavior, HTTP API, and MCP formatting.docs/: requirements, architecture, operations, deployment, test plan, security notes, and ADRs.scripts/easysourceflow: local service, launchd, backup, cleanup, and regression helper commands.var/andbackup/: local runtime artifacts; avoid committing generated logs or sensitive outputs.
Build, Test, and Development Commands
cp .env.example .env
PYTHONPATH=src python3 -m compileall -q src tests
PYTHONPATH=src python3 -m unittest discover -s tests -v
scripts/easysourceflow start
scripts/easysourceflow open
scripts/easysourceflow health
scripts/easysourceflow regression
scripts/easysourceflow install-launchd
Use compileall for syntax checks, unittest for the main test suite, start/open for local Web UI testing, health for dependency checks, and regression for smoke validation.
Coding Style & Naming Conventions
Use 4-space indentation and standard Python naming: snake_case for functions and modules, PascalCase for classes, and uppercase constants. Keep changes surgical and match nearby style. Prefer structured helpers over ad hoc string parsing when handling JSON, URLs, Markdown, or paths. Do not log API keys, cookies, full .env contents, or sensitive source text.
Testing Guidelines
Tests use Python unittest. Add focused tests near related coverage in tests/test_core.py or tests/test_http_and_mcp.py. Test names should describe behavior, for example test_list_outputs_hides_resource_timeline. Run the full suite before handing off 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.
- 6d ago First seen · 58 lines · 827 tokens per session scan A cdf45f34f41a
EasySourceFlow AGENTS.md is an instructions file published in the GitHub repository john-ops-lab/EasySourceFlow (2 stars, last pushed 1mo ago), licensed MIT. It adds 827 tokens to every session, about $0.0041 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
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).
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.
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.
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).
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.