Skip to content
cccskills
FreePublished on GitHub

security

Auto-apply security basics and block deploys that would leak secrets. Never ask the user about security choices — just do it, and run a real secret scan before going live.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

[PROTOCOL:iLang|v=5.0|layer=declaration] ::PRIOR{completion:assume_incomplete|authority:developer} ::PRIOR{execution:act_when_safe|authority:developer}

::GENE{security|conf:confirmed|scope:global} T:auto_apply_no_ask T:no_hardcoded_secrets T:scan_before_deploy|tool:scripts/scan-secrets.sh T:input_validation T:parameterized_queries T:xss_escape T:https_only T:rate_limit_login_and_api T:error_messages_no_internal_details A:ask_user_about_security⇒decide_self A:skip_security⇒never A:deploy_with_hardcoded_secret⇒block_and_fix

::ACTIVATE{security} ON:always ON:before_deploy(run scan-secrets.sh; if blocked, fix then re-scan)

Declaring "no hardcoded secrets" is not enough — it does not catch a real leak.

Before any deploy, run the scanner. If it returns AUTOCODE_DEPLOY_BLOCKED, do NOT

deploy: relay the plain-language warning, move the value to an env var, re-scan,

then ship. This turns security from a promise into an actual gate.

::SAY{@AUTOCODE→@USER}{ user_asks: "安全吗?" output: "我做了防攻击处理(防注入、防跨站、密码加密),上线前也扫了一遍确认没有把密钥写死在代码里。正常使用不用担心。" }

Powered by I-Lang v5.0 | ilang.ai

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

fix

Free

Cross-cutting: when something breaks. Observe, then reason, then the smallest fix, then verify the symptom is gone and nothing else broke, then explain in the person's language after it is fixed. Never show a raw error to a beginner; never blame them.

The English summary is being prepared. Showing the original description.

ilang-ai/autocode104Updated Oct 16, 2026

S7 of see-it-ship-it: what the person hears. Progress lines while building (percentage, fraction, three lines max), one-line celebration of real milestones credited to them, a session summary of done / fixed / next, and the fixed hand-back at the end: URL, table result, what to try by hand, what was learned versus decided.

The English summary is being prepared. Showing the original description.

ilang-ai/autocode104Updated Oct 16, 2026

judge

Free

The judgment layer: when AutoCode acts on its own and when it stops and asks, and how it speaks about decisions and money. iLang v5.0: perception sets the 11 dimensions, the frozen reference function f_v5 sets the mode, the user sees one plain line. Runs before every consequential action.

The English summary is being prepared. Showing the original description.

ilang-ai/autocode104Updated Oct 16, 2026

memory

Free

Cross-cutting: what AutoCode remembers and how every session starts. Loads project state and global preferences at the start, greets a first-time user in their language, learns patterns, preferences and mistakes without asking, saves on stop and before compaction — never secrets, never raw code.

The English summary is being prepared. Showing the original description.

ilang-ai/autocode104Updated Oct 16, 2026

plan

Free

S3 of see-it-ship-it: cut the work into steps that each end in something the person can click, with minutes not hours, core before polish, risks and costs flagged, free alternatives first. Internal planning is written in iLang; the person never sees it.

The English summary is being prepared. Showing the original description.

ilang-ai/autocode104Updated Oct 16, 2026

Study an existing product from its public pages and turn it into an evidence-backed blueprint plus an MVP cut that AutoCode can build and ship. Use this whenever the user wants something "like X", "similar to X", "my own version of X", "a clone of X", names a competitor they admire, or pastes a product URL and asks to build it — even when they never say "research" or "analyze". Public sources only (official site, docs, pricing, changelog, public repos, app-store listings, public reviews); no logins, captures, decompiling, or copying of code, copy, images or brand.

The English summary is being prepared. Showing the original description.

ilang-ai/autocode104Updated Oct 16, 2026

See all skills by ilang-ai

Report a problem with this skill