security-best-practices

security-best-practices is a skill for Codex from sampleXbro/agentsmesh. It costs 73 tokens per session (1,671 once invoked), scanned A, a copy of security-best-practices, MIT.

A security review guide for Python, JavaScript or TypeScript, and Go projects, including their main frameworks.

In plain words
What is it for?
Use it to write safer code, check existing code for major security issues, or prepare a security report with suggested fixes.
Why use it?
It helps identify common security problems and choose safer coding practices. It only runs when security guidance or a review is explicitly requested.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

Good fit Use it to write safer code, check existing code for major security issues, or prepare a security report with suggested fixes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/samplexbro/agentsmesh/security-best-practices
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add sampleXbro/agentsmesh --skill security-best-practices
Clone the repo
git clone --depth 1 https://github.com/sampleXbro/agentsmesh

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for security-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/samplexbro/agentsmesh/security-best-practices/github.svg)](https://agentmods.dev/skills/samplexbro/agentsmesh/security-best-practices)
Your own site
<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/security-best-practices"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/security-best-practices/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for security-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/security-best-practices"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/security-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,671 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.01671
Opus 5.5 $0.00029 $0.00668
Sonnet 5.5 $0.00015 $0.00334
Haiku 4.5 $0.00007 $0.00167

Measured 1mo ago against content hash 6d5dc5058dcb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security-best-practices scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to security-best-practices — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/security-best-practices/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

Security Best Practices

Overview

This skill provides a description of how to identify the language and frameworks used by the current context, and then to load information from this skill's references directory about the security best practices for this language and or frameworks.

This information, if present, can be used to write new secure by default code, or to passively detect major issues within existing code, or (if requested by the user) provide a vulnerability report and suggest fixes.

Workflow

The initial step for this skill is to identify ALL languages and ALL frameworks which you are being asked to use or already exist in the scope of the project you are working in. Focus on the primary core frameworks. Often you will want to identify both frontend and backend languages and frameworks.

Then check this skill's references directory to see if there are any relevant documentation for the language and or frameworks. Make sure you read ALL reference files which relate to the specific framework or language. The format of the filenames is <language>-<framework>-<stack>-security.md. You should also check if there is a <language>-general-<stack>-security.md which is agnostic to the framework you may be using.

If working on a web application which includes a frontend and a backend, make sure you have checked for reference documents for BOTH the frontend and backend!

If you are asked to make a web app which will include both a frontend and backend, but the frontend framework is not specified, also check out javascript-general-web-frontend-security.md. It is important that you understand how to secure both the frontend and backend.

If no relevant information is available in the skill's references directory, think a little bit about what you know about the language, the framework, and all well known security best practices for it. If you are unsure you can try to search online for documentation on security best practices.

From there it can operate in a few ways.

Read the full file on GitHub · 88 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 88 lines · 73 tokens per session scan A 6d5dc5058dcb

Subscribe to this mod's changes

security-best-practices is a skill published in the GitHub repository sampleXbro/agentsmesh (26 stars, last pushed 29d ago), licensed MIT. It adds 73 tokens to every session and 1,671 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to security-best-practices, differing in 9 lines, and is treated as a copy.

Related

Other skills, from other repositories

user-research-cookiy

End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…

cookiy-ai/user-research-skill · 154 tokens

best-practices

Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.

MoizIbnYousaf/Ai-Agent-Skills · 35 tokens

code-documentation

Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.

MoizIbnYousaf/Ai-Agent-Skills · 35 tokens

share-a-library

Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.

MoizIbnYousaf/Ai-Agent-Skills · 41 tokens

update-installed-skills

Use when syncing or updating previously installed skills to their latest version. Always dry-run updates before applying, and check for breaking changes.

MoizIbnYousaf/Ai-Agent-Skills · 31 tokens

pad

Work with the user's Pad workspaces through the Pad tools. Find, read, create and update tasks, bugs, ideas, plans and docs; comment on them, link them, and see what to work on next. Use it whenever the user talks about their Pad projects or items.

PerpetualSoftware/pad · 59 tokens