Audit Gitbook Integration
GitbookIO/integrations
Audit GitBook integrations for script injection, sensitive-data access, unsafe requests, authorization gaps, and manifest or dependency risk.
Security rules for eserstack in TypeScript and Go: secrets, output hygiene, input validation, authorization, injection, SSRF, error sanitization, httpfx hardening, tokens, passwords, cookies…
$ npx skills add eser/stack --skill security-practices -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install eser/stack security-practices --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/security-practices .claude/skills/security-practices && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "security-practices" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/security-practices into .claude/skills/security-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-practices", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/eser/stack/tree/main/.agents/skills/security-practicesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add eser/stack --skill security-practices -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install eser/stack security-practices --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/security-practices .agents/skills/security-practices && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "security-practices" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/security-practices into .agents/skills/security-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-practices", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add eser/stack --skill security-practices -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install eser/stack security-practices --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/security-practices .cursor/skills/security-practices && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "security-practices" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/security-practices into .cursor/skills/security-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-practices", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/eser/stack.git --path .agents/skills/security-practices--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add eser/stack --skill security-practices -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install eser/stack security-practices --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/security-practices .gemini/skills/security-practices && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "security-practices" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/security-practices into .gemini/skills/security-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-practices", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install eser/stack security-practicesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add eser/stack --skill security-practices -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/security-practices .github/skills/security-practices && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "security-practices" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/security-practices into .github/skills/security-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-practices", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add eser/stack --skill security-practices -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install eser/stack security-practices --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/security-practices .opencode/skills/security-practices && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "security-practices" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/security-practices into .opencode/skills/security-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-practices", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
security-practicesSecurity rules for eserstack in TypeScript and Go: secrets, output hygiene, input validation, authorization, injection, SSRF, error sanitization, httpfx hardening, tokens, passwords, cookies…
Security Practices is an agent skill from eser/stack. Security rules for eserstack in TypeScript and Go: secrets, output hygiene, input validation, authorization, injection, SSRF, error sanitization, httpfx hardening, tokens, passwords, cookies, crypto, untrusted files and archives, LLM trust. Use when handling secrets, input, auth, sessions, cookies, crypto, uploads, subprocesses, outbound URLs, prompts, production config or a security review.
Its SKILL.md is about 600 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `evals/triggers.json`, `references/crypto-and-files.md` and `references/http-and-auth.md`).
It sits in Security, covering Web application vulnerabilities, Security review and Authorization and RBAC. It works with TypeScript. The repository describes itself as: The Portability Solution for Your Code! 🚀 Powered By Deno and JavaScript.
Read from SKILL.md and the folder at commit 64939e6. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Security Practices loads about 598 tokens when it runs, and up to ~7.2k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 199 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 199 words (~598 tokens).
“Security rules that apply to every package and service in the repository.”
SKILL.md and 5 other files (references) in .agents/skills/security-practices of eser/stack.
Open the folder on GitHubat commit 64939e6
Security Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Security Practices this skilleser/stack | 128 | — | ~598 | Automated safety check: Pass | Custom licence | |
| Audit Gitbook IntegrationGitbookIO/integrations | 131 | — | ~1.2k | Automated safety check: Pass | None | |
| Security Reviewdeadlock-mod-manager/deadlock-mod-manager | 473 | — | ~1.8k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Security Reviewlangfuse/langfuse | 35k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Security Auditjellydn/my-ai-tools | 123 | — | ~2.9k | Automated safety check: Notes | MIT | |
| Security Reviewgithub/awesome-copilot | 40k | 1 repos | ~2.3k | Automated safety check: Notes | MIT |
GitbookIO/integrations
Audit GitBook integrations for script injection, sensitive-data access, unsafe requests, authorization gaps, and manifest or dependency risk.
deadlock-mod-manager/deadlock-mod-manager
Security code review for Tauri/Rust/TypeScript desktop apps and Hono/oRPC APIs.
langfuse/langfuse
Review Langfuse changes for SSRF, tenant isolation, secret handling, unsafe redirects or uploads, RBAC drift, and client telemetry privacy.
jellydn/my-ai-tools
A skill your agent uses when reviewing code for security vulnerabilities, hardening an application, or deriving security requirements from OWASP/ASVS guidance.
github/awesome-copilot
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching…
trycompai/comp
Check code for the most common, high-risk security vulnerabilities (broken access control, tenant isolation, injection, secrets, SSRF, auth/session, unsafe file handling, mass assignment) before it…
eser/stack
Picks the skills a task needs and maintains the rules in .agents/skills.
eser/stack
System design in eserstack: double-layered hexagonal architecture, explicit adapter composition, public API and CLI surface, request metadata, testing strategy, ADRs.
eser/stack
Language-neutral code quality rules for eserstack, TypeScript and Go.
eser/stack
Interviews the user about a plan, decision or idea in rounds, level by level down a decision tree, until both share one understanding; facts are researched by sub-agents, decisions stay with the user.
eser/stack
Go conventions for eserstack's ajan framework, services and FFI bridge.
eser/stack
TS and JS conventions for eserstack packages: namespace imports, mod.ts entries, cross-runtime APIs, explicit checks, async, tests and laroux React components.
Works with
Categories
Security rules for eserstack in TypeScript and Go: secrets, output hygiene, input validation, authorization, injection, SSRF, error sanitization, httpfx hardening, tokens, passwords, cookies…. Security Practices is an agent skill from eser/stack. Security rules for eserstack in TypeScript and Go: secrets, output hygiene, input validation, authorization, injection, SSRF, error sanitization, httpfx hardening, tokens, passwords, cookies, crypto, untrusted files and archives, LLM trust.
Security Practices fits situations like: handling secrets; production config; A security review.
Run `npx skills add eser/stack --skill security-practices -a claude-code`. Or copy the skill folder (.agents/skills/security-practices in eser/stack) into .claude/skills/security-practices in your project. Claude Code loads it when a task matches its description.
Run `npx skills add eser/stack --skill security-practices -a codex`. Or copy the skill folder (.agents/skills/security-practices in eser/stack) into .agents/skills/security-practices in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add eser/stack --skill security-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/security-practices, .gemini/skills/security-practices, .github/skills/security-practices and .opencode/skills/security-practices in your project.
SKILL.md names no scripts, command-line tools or credentials: Security Practices is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Security Practices has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 598 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.6k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Security Practices: Audit Gitbook Integration (GitbookIO/integrations, 131 stars), Security Review (deadlock-mod-manager/deadlock-mod-manager, 473 stars), Security Review (langfuse/langfuse, 35k stars) and Security Audit (jellydn/my-ai-tools, 123 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
eser (a GitHub user) maintains it in eser/stack, which has 128 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 3, 2026.
Source: eser/stack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.