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.
npx skills add LucasSantana-Dev/sharekit --skill securegit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWrote 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.
[](https://agentmods.dev/skills/lucassantana-dev/sharekit/secure)<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/secure"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/secure/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.
<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/secure"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/secure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.00919 |
| Opus 5.5 | $0.00025 | $0.00368 |
| Sonnet 5.5 | $0.00012 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
secure 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
secure
Use for any work touching secrets, auth, config, deployment, MCP definitions, memory stores, risky dependencies, user input handling, database queries, file operations, cryptography, or infrastructure code.
Integrated guidance: This skill now consolidates three security skill areas:
- Operational security (secrets, credentials, configs, deployment) — check list below
- Web application & infrastructure best practices (HTTPS, CORS, CSRF, rate limiting, auth) — see
references/best-practices.md - Secure coding (SQL injection, XSS, command injection, code patterns across 10+ languages) — see
references/secure-coding.md
Check list
Credentials and secrets
- inline tokens, API keys, bearer headers, or credentials
- secret-bearing files accidentally modified (.env, .pem, .p12)
- hardcoded usernames, passwords, or API keys
- private keys or certificates committed to git
Code security (when reviewing or writing code)
- SQL injection risk (string concatenation, format strings in queries)
- XSS risk (unescaped HTML output, innerHTML, user input in templates)
- Command injection (shell=True, shell expansions with user input)
- Path traversal (user-controlled file paths without validation)
- Code injection (eval, exec with user input)
- Insecure deserialization (pickle, ObjectInputStream, Marshal.load with untrusted data)
- XXE risk (XML parsers with external entity processing enabled)
- Hardcoded secrets or API keys in code
Configuration and deployment
- overbroad permissions or unsafe defaults (CORS *, open security groups, IAM wildcards)
- unencrypted data in transit or at rest
- authentication/validation regressions
- missing rate limiting on auth endpoints
- CSRF protection disabled
- insecure headers or missing HSTS
- Docker containers running as root
- Kubernetes pods running as root or privileged
Dependencies
- dependency vulnerabilities introduced or left unresolved
- outdated library versions with known CVEs
- supply chain risks (typosquatting, unmaintained packages)
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 103 lines · 62 tokens per session scan A e900ef507a9d
secure is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 919 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.