Index of every page on this site: llms.txt
All skills
andreimerlescu avatar

/secure-code-standards

@eb35785
Run it yourself

Mandatory security-conscious engineering for every task that writes, edits, reviews, configures, builds, packages or ships code, scripts, Dockerfiles, CI, config or docs, and especially any task where the agent is handed, discovers or reads a credential, API key, token, password, private key, certificate, connection string, sample .env, or personal data. Forces the agent to classify sensitive material before touching it, keep secrets out of source, binaries, flag defaults, embeds, logs, tests, commits and chat, and to prove it with a scan. Language-agnostic with Go-specific rules; pairs with go-engineering-standards.

  • 19 files
  • 104.4 KB
  • Updated 4 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/andreimerlescu/skills/secure-code-standards

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

AGENTS.snippet.md

≈389 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Security — mandatory skill

For ANY task that writes, edits, reviews, configures, builds or packages code, scripts, Dockerfiles, CI or docs — and ALWAYS when you are handed, find, or read a credential, API key, token, password, private key, certificate, connection string, .env, or a file with a name like keys.txt / secrets.* / *.pem:

  1. Read <SKILL_DIR>/secure-code-standards/SKILL.md first, every time, even for small changes.
  2. Before touching sensitive material, write one SENSITIVE: line in your plan (kind and location, never the value) and follow the Secret Handling Protocol (§2).
  3. Secrets are supplied at runtime from outside the artifact (file path, env, stdin, secret manager). NEVER embed them (go:embed, COPY, include_bytes!), NEVER use them as flag/config defaults, NEVER put them on a command line, in -ldflags, in logs, in tests, in docs, or in your replies.
  4. Missing secret = clear, secret-free error. No fallback literal.
  5. Run bash <SKILL_DIR>/secure-code-standards/scripts/secret-scan.sh (add --literal-file <secret file> and --artifact <binary|image tar> when a secret file exists or anything was built) and quote its SECRET-SCAN SUMMARY block verbatim.
  6. End with the SECURITY CHANGE REPORT from SKILL.md §8. If a secret was ever exposed, say so and tell the user to rotate it.
  7. Never weaken the scanner, .gitignore rules, redaction, tests or this skill to make a finding go away.

Replace <SKILL_DIR> with the real install path. Pair with go-engineering-standards for Go work.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at eb35785. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 weeks ago

README badge

README badge for andreimerlescu/skills/secure-code-standards