Backend Security Coder

Name: Backend Security Coder
Author: dokhacgiakhoa

Listed

dokhacgiakhoa·vlatest·security

Helps with backend development, security as part of implementing security and authentication workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add dokhacgiakhoa/agent-skills-4-vibe-coding-cli --skill backend-security-coder -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dokhacgiakhoa

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 1 Oct 2026

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

Declares what it does: failed
No SKILL.md was found in the skill's directory.
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 dokhacgiakhoa/antigravity-ide at c4a059bbf7.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: c4a059bbf7
Manifest: .agent/skills/backend-security-coder/SKILL.md
Scanned: 0 files
Copies in repo: 3 — all of them scanned

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill helps developers write secure backend code. It can identify potential vulnerabilities in existing code and suggest fixes, as well as generate new code with security best practices incorporated from the start. The tool aims to reduce common coding errors that lead to security breaches.

When to use it

Code Review: When reviewing a developer's work for security flaws before deployment.
New Feature Development: To ensure newly written backend features are secure by default.
Legacy Code Remediation: To identify and fix vulnerabilities in older, existing codebase.
Security Audits: As part of a broader security audit process to automate vulnerability detection.

Key capabilities

Vulnerability identification
Code generation with security best practices
Fix suggestions for identified vulnerabilities

Example prompts

"Review this Python code snippet for SQL injection vulnerabilities."
"Generate a secure API endpoint in Node.js that handles user authentication."
"Suggest fixes for the cross-site scripting (XSS) vulnerability found in this JavaScript function."

Tips & gotchas

The skill's effectiveness is dependent on providing clear and complete code snippets or access to relevant codebase sections. It’s best used as a tool to augment, not replace, human security expertise.