Fnox Security Best Practices
CheckedHelps with security, best practices as part of implementing security and authentication workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add thebushidocollective/han --skill fnox-security-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
thebushidocollective
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned thebushidocollective/han at 19caa51d5f.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 19caa51d5f
- Scanned
- 1 file, 387 lines
About this skill
What it does
This skill provides guidance on implementing security best practices for fnox deployments. It helps users understand common vulnerabilities and how to mitigate them, ensuring a more secure operational environment. The skill offers advice on configuration hardening, access control, and ongoing monitoring to maintain a robust security posture.
When to use it
- When setting up a new fnox deployment and wanting to ensure baseline security from the start.
- During periodic security audits of existing fnox infrastructure.
- To troubleshoot potential security vulnerabilities or incidents within a fnox environment.
- When reviewing configuration changes to assess their impact on overall security.
Key capabilities
- Configuration hardening recommendations
- Access control best practices
- Vulnerability mitigation strategies
- Ongoing monitoring guidance
Example prompts
- "What are the recommended access controls for a fnox deployment?"
- "How can I harden my fnox configuration to prevent unauthorized access?"
- "Give me some tips on how to monitor my fnox environment for security threats."
Tips & gotchas
This skill assumes a basic understanding of fnox architecture and concepts. While it provides best practice recommendations, specific implementation details may require further research based on your unique deployment context.