terminal-legibility
Agent Skill that makes terminal/TUI coding-agent sessions scannable. Audits and sets up a legible theme + font, readable git diffs (delta/difftastic/bat), glamorous markdown rendering (glow/gum), and agent verbosity — then applies a self-formatting output
No outside reports on file
terminal-legibility runs shell or system commands and reads local files; restrict its folder reach, network access, and credentials before installing.
Based on public adoption and transparency signals as of Oct 21, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesReads local filesNOTED
- Command executionRuns shell or system commandsREVIEW
- Network reachLocal or standard API callsLOW
- CredentialsNo API token requiredLOW
- Package sourcenpm (terminal-legibility)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
npx -y terminal-legibilityEverything known
We found nothing about this project in the sources we read (last checked 2026-10-30). That does not mean it has no problems.
0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-30
Popularity grade: D (from public signals such as stars and downloads, not a code review). Graded 2026-10-21.
Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-30.
About Terminal Legibility
Terminal Legibility is an agent skill focused on Developer tools and Files & documents: Agent Skill that makes terminal/TUI coding-agent sessions review. review and sets up a legible theme + font, readable git diffs (delta/difftastic/bat), glamorous markdown rendering (glow/gum), and agent verbosity — then applies a self-formatting output.
It is published on npm as terminal-legibility and hosted on GitHub at rosh100yx/terminal-legibility (4 weekly npm downloads, last repository push on 2026-09-28). Based on its public metadata, its operational scope includes: reads local files, runs shell or system commands.
Setup
These use the package this listing points to. Check the project’s own instructions before running anything.
npm command
npx -y terminal-legibilityWhy this grade
Signal-based grade (1/7 points): public source code. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- Weekly npm downloads
- 4
- Listing last refreshed
- 2026-10-28
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Risks to watch for
- Command execution reach: Public metadata indicates shell, terminal, or container command execution. Run inside an isolated container or VM and require human approval before executing commands.
- Local file read access: Reads local documents or database files. Point it only at the specific files needed for the task so sensitive workspace files remain out of reach.
- Dependency & version pinning: Distributed via npm (terminal-legibility). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.
How to lower the risk
Least-privilege permissions
- Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
- Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.
Network isolation
- Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
- If your IT team can, limit which websites and services it is allowed to contact.
Monitoring
- Check its activity history or logs weekly at first, and look at what it changed or sent.
- Turn on alerts for new logins or unusual usage on any account it connects to.
Red flags to watch for
- It asks for more access than its job requires, or prompts you to paste passwords.
- It suddenly updates with new owners, or starts contacting unfamiliar websites.
Questions
How do I install Terminal Legibility?
Install Terminal Legibility with npm install terminal-legibility or run it directly with npx -y terminal-legibility. For agent integration and configuration flags, see the documentation at github.com/rosh100yx/terminal-legibility. Pin an exact version and pass --ignore-scripts if you want to block post-install hooks.
Are there security reports about Terminal Legibility?
No reports found for this package in our research (last checked 2026-10-30). Terminal Legibility currently holds Grade D (High risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.
Is Terminal Legibility actively maintained?
Terminal Legibility has 4 weekly npm downloads, with its latest repository commit pushed on 2026-09-28. Our directory data was last refreshed on 2026-10-28. Check recent commit activity, release tags, and open issues at github.com/rosh100yx/terminal-legibility before pinning it in production.
What are alternatives to Terminal Legibility?
Compare Terminal Legibility side by side with similar skills in the Related tools section on this page, or browse all skills on AgentArmorHQ.
README badge and team notes
Maintain or use Terminal Legibility? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.
GitHub README Markdown:
[](https://agentarmorhq.com/skills/rosh100yx-terminal-legibility)HTML embed:
<a href="https://agentarmorhq.com/skills/rosh100yx-terminal-legibility"><img src="https://agentarmorhq.com/api/badge/rosh100yx-terminal-legibility" alt="AgentArmorHQ Risk Grade for Terminal Legibility" height="20" /></a>Terminal check:
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "rosh100yx-terminal-legibility"- Compare Terminal Legibility →
- Add to a team allowlist
- Claude and terminal guide →
- Download the PDF guide
Share with your security lead
Need sign-off to use terminal-legibility? Copy this note for Slack, a ticket or a pull request.
### AgentArmorHQ Security Review Memo: terminal-legibility
- **Listing URL:** https://agentarmorhq.com/skills/rosh100yx-terminal-legibility
- **Type:** AI agent skill
- **Risk Grade:** Grade D (High risk signals)
- **Outside Security Advisories on File:** 0
#### Permission & Blast-Radius Signals
- **Local files:** Reads local files
- **Command execution:** Runs shell or system commands
- **Network reach:** Local or standard API calls
- **Credentials:** No API token required
- **Package source:** npm (terminal-legibility)
#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts terminal-legibility`
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.
_Based on public adoption and transparency signals as of Oct 21, 2026. Our opinion, not a code audit or security guarantee._Key facts
- Type
- AI agent skill
- Publisher
- rosh100yx
- Source code
- github.com/rosh100yx/terminal-legibility
- Install command
- npm install terminal-legibility
- Est. context load
- ~93 tokens idle · ~1.5k tokens when active (on-demand skill)
- Popularity
- 4 weekly npm downloads
- Last updated
- 2026-10-28
- Last graded
- 2026-10-21
Community
Discussions for Terminal Legibility
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude