agentleFS
Seeed-ProjectsSeeed-Projects/Seeed-Jetson-DevelopTool/skills/codex/deploy-efficient-vision-engine/AGENTS.md

Seeed-Jetson-DevelopTool / deploy-efficient-vision-engine

AGENTS.md57 starsChanged 4 months agoMITView on GitHub

Use for Seeed Jetson topic "Efficient Multi-Task Vision Inference Engine Deployment on Jetson". Includes local references and execution-safe workflow with prerequisites, commands, and validation checks.

The file

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

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read references/source.body.md first to extract prerequisites and command order.

    line 10
  2. Distinctive:

    Do not skip prerequisite checks.

    line 37
  3. Distinctive:

    If command output differs from expected behavior, pause and ask user before destructive steps.

    line 38
  4. Distinctive:

    Prefer reversible changes and include verification commands.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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

Efficient Multi-Task Vision Inference Engine Deployment on Jetson

Execution model

  1. Confirm board model and JetPack/L4T version before applying commands.
  2. Read references/source.body.md first to extract prerequisites and command order.
  3. Execute steps in smallest reproducible sequence and record command outputs.
  4. Validate final expected results and keep rollback notes.

Source

  • Original markdown: /home/darklee/tmp/jetson-develop/refer-参考完后会清除/Application/Computer_Vision/Efficient_Multi-Task_Vision_Inference_Engine_Deployment_on_Jetson.md
  • Scope: application (Computer_Vision)

Topic summary

Visual Perception Engine is a cutting-edge framework that revolutionizes robotic perception by eliminating redundant computations through shared backbone networks. Unlike traditional approaches where each

Key sections

  • Introduction
  • Prerequisites
  • Technical Highlights
  • Environment Setup
  • Performance Testing
  • Real-time camera input for inference
  • Other Applications
  • Resources
  • Tech Support & Product Discussion

Reference files

  • references/source.md
  • references/source.body.md

Agent instruction

  • Do not skip prerequisite checks.
  • If command output differs from expected behavior, pause and ask user before destructive steps.
  • Prefer reversible changes and include verification commands.

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.