agentleFS
sasuketoriisasuketorii/rev_harness_public/.agents/skills/rust-skills-knowledge-pack/AGENTS.md

rev_harness_public / rust-skills-knowledge-pack

AGENTS.md0 starsChanged 3 months agoApache-2.0View on GitHub

Use rust-skills-master.md as the single source of truth, SKILL.md as the compact skill entrypoint, and rust-skills-sources.md as the source registry. For implementation details, load the relevant file under references/. Hard rules: - Do not implement unbounded concurrency, unbounded channels, request-per-client construction, callback allocations, lock-held awaits, or unchecked crypto nonce/key reuse. - Run cargo audit, cargo deny check, cargo tree -e features, tests, and benchmarks when dependency or hot-path changes are made. - For QUIC/HPKE/TLS/crypto, verify transitive advisories in Cargo.lock, not…

The file

We split this AGENTS.md into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use rust-skills-master.md as the single source of truth, SKILL.md as the compact skill entrypoint, and rust-skills-sources.md as the source …

    line 3
  2. Distinctive:

    Do not implement unbounded concurrency, unbounded channels, request-per-client construction, callback allocations, lock-held awaits, or …

    line 6
  3. Very specific:

    Run cargo audit, cargo deny check, cargo tree -e features, tests, and benchmarks when dependency or hot-path changes are made.

    line 7
  4. Distinctive:

    Treat high-load sending and private communication as authorized, audited, rate-limited, legally compliant systems only.

    line 9
  5. Very specific:

    When browser automation is required, prefer chromiumoxide only for authorized JS-rendered pages, SPA form verification, screenshots, and QA.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

RustSkills Repository Agent Instructions

Use rust-skills-master.md as the single source of truth, SKILL.md as the compact skill entrypoint, and rust-skills-sources.md as the source registry. For implementation details, load the relevant file under references/.

Hard rules:

  • Do not implement unbounded concurrency, unbounded channels, request-per-client construction, callback allocations, lock-held awaits, or unchecked crypto nonce/key reuse.
  • Run cargo audit, cargo deny check, cargo tree -e features, tests, and benchmarks when dependency or hot-path changes are made.
  • For QUIC/HPKE/TLS/crypto, verify transitive advisories in Cargo.lock, not only top-level crate versions.
  • Treat high-load sending and private communication as authorized, audited, rate-limited, legally compliant systems only.

Browser Automation/CDP

When browser automation is required, prefer chromiumoxide only for authorized JS-rendered pages, SPA form verification, screenshots, and QA. Static HTML should remain reqwest + scraper. Do not add stealth or anti-bot bypass workflows as standard implementation guidance. Browser processes must be pooled, bounded, timeout-protected, and kill-switchable.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.