little-canary
Reduces prompt injection risk by testing untrusted input against a lightweight model before it reaches production systems, catching behavioral anomalies that…
Detects prompt injection by its effect on a sacrificial canary model, not just pattern matching: untrusted input hits a powerless model first, a behavioral check reads the residue, and it returns block, flag, or pass before your primary model acts. Inbound preflight sensor, not a guarantee.
- Ask Claude to screen user inputs for prompt injection before processing sensitive requests
- Automatically flag suspicious prompts that attempt to override system instructions or constraints
- Test untrusted third-party data inputs against injection attacks before feeding to production models
Reduces prompt injection risk by testing untrusted input against a lightweight model before it reaches production systems, catching behavioral anomalies that signature detection misses.
Teams deploying LLM applications handling user-supplied prompts or external data sources.
https://github.com/hermes-labs-ai/little-canary
By hermes-labs-ai
How to Get It
claude plugins install hermes-labs-ai/little-canary
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Screen user inputs for prompt injection before processing sensitive requests
Trust Signals Auto-scanned
Community Pulse Quiet
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 32 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 32 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.