Install
$ agentstack add skill-brunov21-ferrisgrid-cli-ferrisgrid-install ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
FerrisGrid Install
Use this when a machine needs the normal published FerrisGrid CLI. Only use a local checkout when the user explicitly asks for source development.
Steps
- Check Rust is available and whether
ferrisgridis already onPATH:
cargo --version
which ferrisgrid
If Rust is missing, tell the user Rust/Cargo must be installed before the published CLI can be installed.
- Install or update the published CLI from crates.io. The crates.io package name is
ferrisgrid-cli; it installs the executable namedferrisgrid:
cargo install ferrisgrid-cli
If this fails with DNS, crates.io index, or other network-related errors in a sandboxed agent environment, retry the same command with the normal escalation flow because cargo install needs network access.
- Confirm the installed binary is available and responds:
which ferrisgrid
ferrisgrid help
Do not use ferrisgrid --version as the verification command unless the CLI has added that command; older releases report it as an unknown command.
- Run diagnostics:
ferrisgrid doctor
On macOS, doctor can exit successfully while reporting native capture problems such as CoreGraphics returned no displays and screens: 0. Treat that as an environment or permission issue, not an install failure, if ferrisgrid help and the fake backend smoke test work.
- Smoke-test capture without touching the real desktop:
ferrisgrid observe --backend fake
This verifies the CLI protocol and output writing path even when native desktop capture is unavailable.
Development from source
Use these commands only inside a local FerrisGrid checkout when modifying the project:
cargo build -p ferrisgrid-cli
cargo test --workspace
cargo run -q -p ferrisgrid-cli -- doctor
Notes
- On macOS, real capture needs Screen Recording permission.
- On macOS, real capture may also require running from a logged-in desktop session.
- Real actions need Accessibility permission.
- Default output is
.ferrisgrid/. - Use
--backend fakeonly for protocol smoke tests; normal usage should use the native backend.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: BrunoV21
- Source: BrunoV21/FerrisGrid-CLI
- License: MIT
- Homepage: https://brunov21.github.io/FerrisGrid-CLI/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.